Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Case sensitivity when parsing 'control' like files. #57

Open
ebikt opened this issue Aug 22, 2016 · 1 comment
Open

Case sensitivity when parsing 'control' like files. #57

ebikt opened this issue Aug 22, 2016 · 1 comment

Comments

@ebikt
Copy link
Contributor

ebikt commented Aug 22, 2016

https://wiki.debian.org/RepositoryFormat#A.22Release.22_files:

The "Release" files, "Packages" and "Sources" indicies, and files called "Index" that are used for translations and differences are control files, as defined in Policy, Chapter 5. In addition to the rules for control files, field names shall be generated using the case defined in this document, that is, code creating repositories shall be case-sensitive, but code reading repositories should not be case-sensitive.

I guess this aplies also to .changes files.

It will be neat to have option to either ignore case or require proper case (i.e., "raise error" when decoding key that matches key from struct only case-insensitively).

@paultag
Copy link
Owner

paultag commented Aug 22, 2016

Good point! Perhaps enforce a canonization, since all of them follow the Foo-Bar-Baz convention; but maybe that isn't actually good enough.

I also wonder what the expected behavior for:

Foo: 1
foo: 1

is

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants