[opensuse-factory] rfc name for new library package
Hello, I've been maintaining and using a .so package of: http://freshmeat.net/projects/jbigkit for some time in a home repo, and recently got it added to graphics: https://build.opensuse.org/package/show?package=jbig-kit&project=graphics Next I want to submit it for inclusion in Factory so that it can then be used to add jbig support to libtiff, hylafax, ghostpdl, ghodtscript, others. Some of these already have jbig support but it's via direct code inclusion. But for example ./configure in current libtiff will automatically find and use the jbig include files and shared lib if the package above is installed. The change to the tiff3 .spec is merely to add jbigkit-devel to buildrequires. I've been doing that in my home repo for a while. However before submitting to Factory I want to see if the package name should be changed so that we're not either stuck with a stupid name forever, or change the name sometime later after it's been in use already. The only reason the package name is "jbigkit" or "JBIG-KIT" is because that's the name of the upstream tar. the only reason the upstream tar is named that is because that's what that is, a kit for demonstrating jbig and devoloping with it. The upstream code is really meant to be included directly within other programs, not packaged as a shared library. But the library itself is just "jbig" or "jbig2" So request for comments, I think I should: * Change the base package name to just jbig or jbig%{major}. * Have only the sample binaries and docs in the base package. * Move the libraries into a libjbig%{major} package Basically just like jpeg https://build.opensuse.org/package/view_file?file=jpeg8.spec&package=jpeg8&project=graphics&srcmd5=c2bb64fe01a14d7a791f3b387357628e And pretty much ignore the fact that the upstream tar is named "jbig-kit". The installed stuff is not a "kit" but a finished product that uses the original kit. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, 14 Apr 2011 14:23:00 -0400, "Brian K. White"
So request for comments, I think I should:
* Change the base package name to just jbig or jbig%{major}. * Have only the sample binaries and docs in the base package. * Move the libraries into a libjbig%{major} package
According to the shared library policy you have to put the shared library in a package named libjbig%{major} anyway and it would be lots of unnecessary work having to rename the spec file with every change in the library major version. So I'd stick with the tarball name for the main package that would only contain binaries. I'd only include the docs if they describe the sample binaries. If the docs mainly describe the library and it's API I'd put them in the -devel package that's needed for the headers and the .so symlink. Philipp -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Brian K. White wrote:
the only reason the upstream tar is named that is because that's what that is, a kit for demonstrating jbig and devoloping with it. The upstream code is really meant to be included directly within other programs, not packaged as a shared library.
Have you tried contacting upstream to include your shared lib patch nevertheless? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Brian K. White
-
Ludwig Nussel
-
Philipp Thomas