[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFC: libc6 policy supplement 2nd try

>     packages as follows [1]. Some packages (mostly from base) may use
>     locations in /lib. 
>        based on  | package name | library location
>        --------------------------------------------
>          libc6   |   libfoo     | /usr/lib/libfoo.so.<ver>
>          libc5   |   libfoo-g   | /usr/lib/libc5-compat/libfoo.so.<ver> [2]

Isn't that the other way around: the libc6 version with g, and the
libc5 version without? (This convention would ensure that somebody
with an old (from bo, libc5) libfoo and a new libfoo-g would have
the same library twice, and other libc6 packages couldn't just
depends: libfoo, cause there are now two libfoo's (a libc5 and a libc6 one).

>       based on  | package name        | hierarchy locations
>       ---------------------------------------------------------------
>       libc6     | libfoo-dev          | /usr/{lib,include}
>       libc5     | libfoo-g-altdev     | /usr/i486-linuxlibc1/{lib,include}

Here again, unless I'm really confused, the "g" is mixed up.

joost witteveen, joostje@debian.org
#!/usr/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: