Bug#509935: decide whether Uploaders is parsed per RFC 5322
Jakub Wilk <firstname.lastname@example.org> writes:
> I propose the following simple solution to this bug:
> - Let's forget about RFC 822/5322 compatibility, as it would introduce
> only needless complexity.
> - Let's allow any punctuation characters in maintainer names and e-mail
> addresses *except* "<" and ">".
> This way comma is completely disambiguated: it splits the field if and
> only it's preceded by the ">" character. I.e. you can use the following
> Perl regex to split the field: /\>\K\s*,\s*/.
Oh, hm, yeah, that would work.
>> Currently, the only way to express such a name that works with our
>> existing tools is to drop the comma, since several programs blindly
>> split on commas when parsing the field.
> Let's fix them, then. :) I volunteer to fix lintian and dd-list. Do you
> know any other tools that parse Uploaders?
dak, of course, but it sounds from your message like it's already doing
the right thing. The PTS and DDPO -- I'm not sure what gets that data
into those systems. UDD?
I think your solution sounds excellent.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>