Third party repositories and glibc-solibs package conflict

General talk about packaging procedures and packages.
Post Reply
User avatar
zAchAry
Posts: 804
Joined: 11. May 2010, 09:02
Location: Israel

Third party repositories and glibc-solibs package conflict

Post by zAchAry »

Maybe this should be at the Problems section... Oh, well.

I know that you're already aware of the mismatch with glibc in contrast to glibc-solibs package name problem, which makes package installation from some third-party repositories less easy.

Is this going to change?
i.e. renaming the glibc package (ftp.gwdg.de) to glibc-solibs or should I ask the admins/communities of the other repositories to change their glibc-solibs to glibc OR ask them to add glibc (like seamonkey|seamonkey-solibs) if it won't make any mess?
Image
Help to make Slackware easier Donate to Salix
User avatar
thenktor
Salix Wizard
Posts: 2426
Joined: 6. Jun 2009, 14:47
Location: Franconia
Contact:

Re: Third party repositories and glibc-solibs package confli

Post by thenktor »

The dep has to be glibc|glibc-solibs because both packages are not the same. They both include the needed libs, but only glibc contains headers, too.
Image
burnCDDA (burns audio CDs)
geBIERt (German beer blog)
Post Reply