On Tue, May 12, 2015 at 09:21:13AM +0900, Charles Plessy wrote:
> Le Mon, May 11, 2015 at 11:30:54AM +0200, Bill Allombert a écrit :
> >
> > We should document that to prevent /lib64 to be used for wrong purpose.
> >
> > > In any case I'm not quite sure whether shipping files in lib64 in amd64
> > > packages (juffed/juffed-dev and zynaddsubfx-dssi do this now) is OK.
> >
> > I only found
> > zynaddsubfx-dssi: /usr/lib64/dssi/libzynaddsubfx_dssi.so
> > which I think is a RC bug.
> >
> > But note that this bug is about /lib64, not /usr/lib64
>
> Hi Bill,
>
> while the title is only about /lib64, the main text of the original message
> in for this bug is about /lib64 and /usr/lib64.
OK, here a new patch.
Seconds welcome!
Cheers,
--
Bill. <[email protected]>
Imagine a large red swirl here.
diff --git a/policy.sgml b/policy.sgml
index 404dc73..f9fdbf7 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -6955,12 +6955,13 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)
character.
</p>
</item>
<item>
<p>
- The requirement for amd64 to use <file>/lib64</file>
- for 64 bit binaries is removed.
+ The requirement for amd64 to use <file>/lib64</file> for
+ 64 bit binaries is removed. Only the dynamic linker is
+ allowed to use this directory.
</p>
</item>
<item>
<p>
The requirement for object files, internal binaries, and
@@ -6983,10 +6984,14 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)
use in cross-installation of library packages from other
architectures, as part of <tt>multiarch</tt>.
</footnote>
</p>
<p>
+ No package for a 64 bit architecture may install files
+ in <file>/usr/lib64/</file> or in a subdirectory of it.
+ </p>
+ <p>
The requirement for C and C++ headers files to be
accessible through the search path
<file>/usr/include/</file> is amended, permitting files to
be accessible through the search path
<file>/usr/include/<var>triplet</var></file> where
