Stephan Kulow wrote:

Am Mittwoch 10 Juni 2009 schrieb Vincent Untz:

...

Hi,

What's the proper way of naming a lang package that goes with a shared library following the shared library policy?

Eg: the libgsasl source package has a libgsasl7 package. So far so good. But it has translations, so should the translations go in libgsasl-lang or libgsasl7-lang?

If it's a libgsasl.mo, then the files will conflict anyway, so there is little point in pretending you can install them side by side: libgasl-lang.

But there comes a catch: you can't require that package from the library - or only using a >= - otherwise you won't be able to install the libraries side by side.

We can extend packaging rules in the spirit of the shared library packaging policy: - s/soname/textdomain/g - s/libfoo{xxx}/foo{xxx}-lang/g ... and you have a packaging rule. It will fulfill exactly what you expect: - packages with different name will not conflict - shared library knows the translation domain and you can require package of correct name. - when upstream changes translation domain, you will get a new dependency nad new name of the package. => you can require package of that name from a shared library package -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org