On 12-Apr-2017, gregor herrmann wrote: > Maybe someone has an idea how we can simulate something like > case-insensitive method names?
For resolving this bug, I think the method names don't need to change and don't need to be case-insensitive. The only behaviour needing resolution for this bug report is that valid field names from the control file are rejected. Policy does not mandate the way a Perl library makes accessors on its objects, for example. It merely mandates that the names from the control files must be interpreted case-insensitive. > On Mon, 10 Apr 2017 22:37:28 +1000, Ben Finney wrote: > > For example, the names “vcs-git”, “Vcs-Git”, “VCS-Git”, “vcS-gIt” > > should all be interpreted as the same field name by > > ‘libdebian-source-perl’. So, with the above example, if each those field names were accepted, and they all map to the Perl object accessor ‘Vcs_Git’, and other Perl code still needed to spell the *accessor* name that way, that would IMO be compliant with Policy and would resolve this bug report. -- \ “I fly Air Bizarre. You buy a combination one-way round-trip | `\ ticket. Leave any Monday, and they bring you back the previous | _o__) Friday. That way you still have the weekend.” —Steven Wright | Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
