On Sun, 7 Jun 2009 18:45:53 +0200 Raphael Hertzog <hert...@debian.org> wrote:
> On Sun, 07 Jun 2009, Neil Williams wrote: > > Is there some hidden assumption that the filename must match the Vendor > > because the existing default file does not follow that convention, at > > least as far as case-sensitivity is concerned. (debian vs Debian). > > Yes. Case-sensitivity is taken care of (we try files named $vendor, > lc($vendor), ucfirst($vendor)), but that's the only difference > allowed between the name of the vendor and the filename. That isn't true because --vendor accepts the file, DEB_VENDOR fails. > There's no documentation of the origins files for now and I'm not sure > what you want me to do to resolve this bug. The behaviour with DEB_VENDOR should match the behaviour with --vendor and there should be some way of handling vendor names that include spaces without needing to use quote marks when using the environment variables or --vendor options. It is inconsistent that the command line option works one way and the environment variable works another way. It would be better to look only for the matching filename and then use the value for the field from that file. If the supplied argument matches the filename, why bother cross-checking that with the Vendor: field inside the file? I would have thought that the field can be the longer, descriptive title and the filename can be a shortened version. Currently, if the file specified originally has the Vendor changed from the correct title "Emdebian Crush" to the corrupted form "Emdebian-Crush", then dpkg-vendor works in the same way with both forms. This change should not be necessary. What is the reason for the duplicate check? -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
