Am Montag, 20. Mai 2002, 21:09:40 Uhr MET, schrieb Alexander Skwar: > The package is numed this way, because of the libname policy. It > dictates, that the package name contains the version of the .so file it > contains. Without looking in the package, I'd assume that libxine0.9.9 > contains a libxine.so.0.9.9. This is to allow parallel installations of > the same library in different versions - granted, doesn't make sense for > -devel packages.
So this is a proposal for a new library naming scheme: library package stay the same and all devel packages have to be renamed. That will be quite a lot of work :-( But you're right, it makes sense if you cannot install two devel packages of the same library. It's just bad for buildrequirements, because if you put buildRequires: libfoo3-devel in your spec file you expect the devel package to the API of libfoo.so.3, that's the easiest way to specify that. CU -- G�tz Waschk <> student of computer science <> university Rostock http://wwwstud.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
