Re: Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

2006-05-19 Thread Goswin von Brederlow
Junichi Uekawa <[EMAIL PROTECTED]> writes: > Hi, > >> I'm not suggesting splitting the dirs. Just the way the link is setup. >> >> I'm suggesting creating it in the maintainer scripts instead of the >> data.tar.gz so packages that do ship files in (/usr)/lib64 don't make >> libc6 unupgradable. >

Re: Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

2006-05-19 Thread Junichi Uekawa
Hi, > I'm not suggesting splitting the dirs. Just the way the link is setup. > > I'm suggesting creating it in the maintainer scripts instead of the > data.tar.gz so packages that do ship files in (/usr)/lib64 don't make > libc6 unupgradable. On debootstrap install, libc6 postinst isn't actually

Re: Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

2006-05-19 Thread Gabor Gombas
On Fri, May 19, 2006 at 10:58:33AM +0200, Goswin von Brederlow wrote: > Local admins are already allowed to convert directories into links, > e.g. to move parts ot the directory tree to another disk. According to Steve Langasek in Message-ID: <[EMAIL PROTECTED]> that's not allowed and you should

Re: Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

2006-05-19 Thread Stephen Frost
* Aurelien Jarno ([EMAIL PROTECTED]) wrote: > The FHS is actually not very clear, as it says 64-bit libraries should > be in (/usr)/lib64, whereas system libraries should be in (/usr)/lib. > This is a contradiction for a pure 64-bit system. The FHS is very clear about the path to the 64bit linke

Re: Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

2006-05-19 Thread Andreas Jochens
On 06-May-19 11:02, Goswin von Brederlow wrote: > Andreas Jochens <[EMAIL PROTECTED]> writes: > > Anything which makes it easier to violate this simple policy > > will lead to a mixed usage of /usr/lib and /usr/lib64 and consequently > > to problems which could be difficult to disentangle later. >

Re: Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

2006-05-19 Thread Goswin von Brederlow
Andreas Jochens <[EMAIL PROTECTED]> writes: > Hello Aurelien, > > On 06-May-19 04:15, Aurelien Jarno wrote: >> [Ccing: amd64 and dpkg developers as they are concerned by this subject] >> Currently the (/usr)/lib64 -> /lib symlink is shipped in the libc6 >> package. Goswin von Brederlow asked for

Re: Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

2006-05-19 Thread Goswin von Brederlow
Aurelien Jarno <[EMAIL PROTECTED]> writes: > Currently the (/usr)/lib64 -> /lib symlink is shipped in the libc6 > package. Goswin von Brederlow asked for this link to be created in the > postinst instead, so that packages could install files in both > (/usr)/lib and (/usr)/lib64 directories. > > I

Re: Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

2006-05-18 Thread Andreas Jochens
Hello Aurelien, On 06-May-19 04:15, Aurelien Jarno wrote: > [Ccing: amd64 and dpkg developers as they are concerned by this subject] > Currently the (/usr)/lib64 -> /lib symlink is shipped in the libc6 > package. Goswin von Brederlow asked for this link to be created in the > postinst instead, s

Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

2006-05-18 Thread Aurelien Jarno
[Ccing: amd64 and dpkg developers as they are concerned by this subject] Hi all, [Short introduction to understand the problem] I am asking here for help to take a decision. As some of you may know, on amd64, the main libraries are installed into (/usr)/lib, with (/usr)/lib64 being a symlink