* Josip Rodin <[EMAIL PROTECTED]> [010426 14:54]:
> Our inability to get this into Policy is appaling, isn't it? :<

Especially since both you and Wichert have put effort into this -- that
is two possible seconds for a proposal. I've taken a closer look at the
policy-process text and I do not think I am actually allowed to make
proposals. (Though in the section about seconding, it makes especial
reference to "registered Debian developers". Perhaps for the purposes of
getting this bug taken care of, simply being An Interested User counts
for proposals. If this is in error (Julian/Manoj?) let me know and I'll
stop proposing things. :)

> They need to be exempt from the rule for shlibs file, too.
> 
> See my attempt in #66023...

Aye, too true. It may be easier for the proposal to not decide the paths
involved -- it should be sufficient to say which paths are *not*
allowed. Another shot (again placed in the public domain).:


--- policy.txt  Thu Apr 26 19:31:26 2001
+++ so-policy.txt       Thu Apr 26 19:57:17 2001
@@ -2313,6 +2313,15 @@
      library links point to them, just before `dpkg' continues the
      installation and removes the links!
 
+     It is the case that some packages supply plugins intended for
+     internal use only and these plugins are often technically shared
+     libraries. If the plugin files are not installed in the default
+     search path of `ld.so' (currently /lib, /usr/lib), or in common
+     locations specified in `/etc/ld.so.conf' (such as /usr/X11R6/lib),
+     then the package's plugins are not required to comply with the
+     paragraph requiring symbolic links nor the `shlibs' sections
+     following.
+
 
 9.1. The `shlibs' File Format
 -----------------------------

-- 
Earthlink: The #1 provider of unsolicited bulk email to the Internet.
--- policy.txt  Thu Apr 26 19:31:26 2001
+++ so-policy.txt       Thu Apr 26 19:57:17 2001
@@ -2313,6 +2313,15 @@
      library links point to them, just before `dpkg' continues the
      installation and removes the links!
 
+     It is the case that some packages supply plugins intended for
+     internal use only and these plugins are often technically shared
+     libraries. If the plugin files are not installed in the default
+     search path of `ld.so' (currently /lib, /usr/lib), or in common
+     locations specified in `/etc/ld.so.conf' (such as /usr/X11R6/lib),
+     then the package's plugins are not required to comply with the
+     paragraph requiring symbolic links nor the `shlibs' sections
+     following.
+
 
 9.1. The `shlibs' File Format
 -----------------------------

Attachment: pgpDcex5ySjTp.pgp
Description: PGP signature

Reply via email to