Third party repositories and glibc-solibs package conflict
Posted: 12. Nov 2010, 19:35
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?
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?