Christian Franke skrev 2011-12-16 21:25: > Corinna Vinschen wrote: >> On Dec 15 14:13, Eric Blake wrote: >>> On 12/15/2011 01:59 PM, Christopher Faylor wrote: >>>> I think it's lame to have something like, e.g., >>>> >>>> /usr/src/openssh-5.6p1-2/openssh-5.6p1-2 >>>> /usr/src/binutils-2.22.51-1/binutils-2.22.51-1 >>>> >>>> sitting in my /usr/src. I find that nearly as objectionable as having >>>> files littered in /usr/src. >> I don't like /usr/src/binutils-2.22.51-1/binutils-2.22.51-1 either, but >> it's much less objectionable than having /usr/src littered with the >> content of package files. > > Attached is a new patch which takes a different approach. > It handles both cases on the fly during installation. > > /usr/src/binutils-2.22.51-1/* will be installed as before, but > /usr/src/blacklist.txt will be installed as > /usr/src/ca-certificates-1.78-1/blacklist.txt > > This would break directory structure for packages which contain both, a > PACKAGE-VERSION subdir and toplevel files. Such packages might exist or not. > If yes, these should probably be fixed first. > > Yes, I agree that this is a hack. But someone might agree that this is a > useful hack :-)
If we don't play games like this in setup.exe, it is still possible to create a structure beneath /usr/src/foo with different packages with some foo relation. With an automatic remapping in setup, that is no longer possible. Not that I know of any such structure at this time, but something to consider... Cheers, Peter
