[opensuse-packaging] Shared Library Policy Questions
goffice contains a shared library as well as shared files (glade files
for UI elements exposed by the library) and plugins. Its install dirs
use a versioned dir system so it is parallel installable.
Questions:
1) As per exception #3 in the shlib policy the glade files could go in
libgoffice-0_6-6 or in goffice-0_6. If the latter, I assume
libgoffice-0_6-6 needs to explicity require goffice-0_6
2) Do plugins go in goffice-0_6-plugins or libgoffice-0_6-plugins?
3) Could the plugins be "Recommend"ed by libgoffice-0_6-6?
Perhaps we should add an example with parallel installable versioning?
-JP
--
JP Rosevear
On Wed, 30 Jan 2008, JP Rosevear wrote:
goffice contains a shared library as well as shared files (glade files for UI elements exposed by the library) and plugins. Its install dirs use a versioned dir system so it is parallel installable.
Is the shared library only used by goffice? If so there is no reason to separate it from the package containing the binary applications linking against it.
Questions:
1) As per exception #3 in the shlib policy the glade files could go in libgoffice-0_6-6 or in goffice-0_6. If the latter, I assume libgoffice-0_6-6 needs to explicity require goffice-0_6
Does the shared library load these files? If so they can go into the shared library package (if they would have unversioned dirs it would need a libgoffice-0_6-data package). Requiring goffice from libgoffice sounds backward and I would recommend against it, so putting the files in the shlib package sounds right here.
2) Do plugins go in goffice-0_6-plugins or libgoffice-0_6-plugins?
The policy says nothing about this, so I would recomment existing practice. From my POV it should be goffice-0_6-plugins, but the question is again - is libgoffice only used by goffice? If not, are the plugins loaded by the shared library then? Then they are related to the shlib and the package should be called libgoffice-0_6-plugins.
3) Could the plugins be "Recommend"ed by libgoffice-0_6-6?
If they are related to the library and not the application, sure (see above).
Perhaps we should add an example with parallel installable versioning?
Feel free to add one ;) (it's a wiki after all)
Richard.
--
Richard Guenther
On čtvrtek 31 leden 2008, Richard Guenther wrote:
On Wed, 30 Jan 2008, JP Rosevear wrote:
2) Do plugins go in goffice-0_6-plugins or libgoffice-0_6-plugins?
The policy says nothing about this, so I would recomment existing practice. From my POV it should be goffice-0_6-plugins, but the question is again - is libgoffice only used by goffice? If not, are the plugins loaded by the shared library then? Then they are related to the shlib and the package should be called libgoffice-0_6-plugins.
In ImageMagick the plugins are loaded by the library, so I packaged them in a versioned directory in the lib subpackage. -- Vladimir Nadvornik --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thu, 31 Jan 2008, Vladimir Nadvornik wrote:
On ctvrtek 31 leden 2008, Richard Guenther wrote:
On Wed, 30 Jan 2008, JP Rosevear wrote:
2) Do plugins go in goffice-0_6-plugins or libgoffice-0_6-plugins?
The policy says nothing about this, so I would recomment existing practice. From my POV it should be goffice-0_6-plugins, but the question is again - is libgoffice only used by goffice? If not, are the plugins loaded by the shared library then? Then they are related to the shlib and the package should be called libgoffice-0_6-plugins.
In ImageMagick the plugins are loaded by the library, so I packaged them in a versioned directory in the lib subpackage.
This is of course also fine. If they are large and optional it
might be good to separate them from the library and make the
dependency a recommends, so they can be for example omitted from
the single-CD image.
Richard.
--
Richard Guenther
On Thu, 2008-01-31 at 11:03 +0100, Richard Guenther wrote:
On Wed, 30 Jan 2008, JP Rosevear wrote:
goffice contains a shared library as well as shared files (glade files for UI elements exposed by the library) and plugins. Its install dirs use a versioned dir system so it is parallel installable.
Is the shared library only used by goffice? If so there is no reason to separate it from the package containing the binary applications linking against it.
goffice it self is a shared library not an applicate (gnucash and gnumeric use it at least).
Questions:
1) As per exception #3 in the shlib policy the glade files could go in libgoffice-0_6-6 or in goffice-0_6. If the latter, I assume libgoffice-0_6-6 needs to explicity require goffice-0_6
Does the shared library load these files? If so they can go into the shared library package (if they would have unversioned dirs it would need a libgoffice-0_6-data package). Requiring goffice from libgoffice sounds backward and I would recommend against it, so putting the files in the shlib package sounds right here.
Yes, it loads them and yes the they are in a versioned dir.
2) Do plugins go in goffice-0_6-plugins or libgoffice-0_6-plugins?
The policy says nothing about this, so I would recomment existing practice. From my POV it should be goffice-0_6-plugins, but the question is again - is libgoffice only used by goffice? If not, are the plugins loaded by the shared library then? Then they are related to the shlib and the package should be called libgoffice-0_6-plugins.
Yes, the plugins are loaded by the shared library.
3) Could the plugins be "Recommend"ed by libgoffice-0_6-6?
If they are related to the library and not the application, sure (see above).
Ok.
Perhaps we should add an example with parallel installable versioning?
Feel free to add one ;) (it's a wiki after all)
Additionally, should packages that can be parallel installed always be
packaged as such or only if the need arises?
Thanks,
-JP
--
JP Rosevear
On Thu, 31 Jan 2008, JP Rosevear wrote:
Additionally, should packages that can be parallel installed always be packaged as such or only if the need arises?
I would argue for always, as it is usually difficult to later fix
packaging of pkg-1.0 if you want to install pkg-2.0 in parallel.
At least if it is not too much work. (Who wants to install two
openoffice versions in parallel?)
Richard.
--
Richard Guenther
participants (3)
-
JP Rosevear -
Richard Guenther -
Vladimir Nadvornik