[opensuse-packaging] The ROOT framework packages
Hi, I'm working on packaging the ROOT analysis framework, and need some advices. The package is currently located in the science project: https://build.opensuse.org/package/show?package=root&project=science The special thing about root is that it contains a C interpreter, cint. Therefore root needs all the header files of the framework librarys to run. I don't know how I should add these depencies on the devel packages. The libraries itself do not depend on the devel package, and the root-bin package also does not depend on the devel packages. But when a library is installed cint needs the corresponding -devel package of this library to use it. I think making every library depend on its devel package is not so nice, but in principle this is what is needed... Another thing are dependencies between devel packages. Because some header files include header files from other librarys one needs also the other library and devel package to be used by with cint. Is it possible to resolve such dependencies an automatical way? Doing this by hand will be a lot of work... And perhaps you can give me a hint about the root-ttf package. This package will most probably not pass the legal review, because it conains Microsoft fonts. Fedora uses a package that loads the fonts from the root ftp server on installation, but this is not allowed with the build service... And when someone can give me some hints about resolving some of these rpmlint warnings I would be happy: * unstripped-binary-or-object * shlib-policy-missing-lib * devel-file-in-non-devel-package (These files are required by cint, and therefore can not go in a devel package) Thanks, Thomas -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
25 ноября 2012 11:03:26 Thomas Zimmermann написал(а):
And perhaps you can give me a hint about the root-ttf package. This package will most probably not pass the legal review, because it conains Microsoft fonts. Fedora uses a package that loads the fonts from the root ftp server on installation, but this is not allowed with the build service...
We can use the same way as package fetchmsttfonts. https://build.opensuse.org/package/show?package=fetchmsttfonts&project=openSUSE%3AFactory -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am Sonntag, 25. November 2012, 14:23:48 schrieb Dmitry Roshchin:
We can use the same way as package fetchmsttfonts. https://build.opensuse.org/package/show?package=fetchmsttfonts&project=openS USE%3AFactory
Ok, perhaps this are also the same fonts as the one provided by root-ttf, and I can make the root-ttf just depend on this package and put a symbolic link to the mstfonts package into the package. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
* shlib-policy-missing-lib
Hi Thomas, splitting root into subpackages it may make sense from the point of view of the developers and edge users... the mainstream user wants the things just installed and does not care about these subtleties... I propose you to create a binary package eg root, -devel, -doc and -examples if any... what is important with root would be to have all or almost all the capabilities on at build time and installed. this we can solve later. it is useful if one want different versions of the lib installed in parallel... regards, Alin On Sun 25 Nov 2012 11:03:26 Thomas Zimmermann wrote:
Hi, I'm working on packaging the ROOT analysis framework, and need some advices. The package is currently located in the science project: https://build.opensuse.org/package/show?package=root&project=science
The special thing about root is that it contains a C interpreter, cint. Therefore root needs all the header files of the framework librarys to run.
I don't know how I should add these depencies on the devel packages. The libraries itself do not depend on the devel package, and the root-bin package also does not depend on the devel packages. But when a library is installed cint needs the corresponding -devel package of this library to use it. I think making every library depend on its devel package is not so nice, but in principle this is what is needed...
Another thing are dependencies between devel packages. Because some header files include header files from other librarys one needs also the other library and devel package to be used by with cint. Is it possible to resolve such dependencies an automatical way? Doing this by hand will be a lot of work...
And perhaps you can give me a hint about the root-ttf package. This package will most probably not pass the legal review, because it conains Microsoft fonts. Fedora uses a package that loads the fonts from the root ftp server on installation, but this is not allowed with the build service...
And when someone can give me some hints about resolving some of these rpmlint warnings I would be happy: * unstripped-binary-or-object * shlib-policy-missing-lib * devel-file-in-non-devel-package (These files are required by cint, and therefore can not go in a devel package)
Thanks, Thomas -- Without Questions there are no Answers!
Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi Alin
splitting root into subpackages it may make sense from the point of view of the developers and edge users... the mainstream user wants the things just installed and does not care about these subtleties...
I propose you to create a binary package eg root, -devel, -doc and -examples if any... what is important with root would be to have all or almost all the capabilities on at build time and installed.
This is true, but then also the root package has to depend on it's devel package. And having the possiblility to install is an advantage that does not cost much but in some cases is an advantage. Since a few weeks also a "root" package was built that just depended on all other packages, but somehow this is not build anymore...
* shlib-policy-missing-lib
this we can solve later. it is useful if one want different versions of the lib installed in parallel...
Ok, then this will be very complicated to fix... The libs are already installed in versioned subdirectorys, but root requires them to be installed in the non-versioned directorys, and therefore there are links from the nonversioned directory to the versioned one... Regards Thomas
regards,
Alin -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Ok, then this will be very complicated to fix... The libs are already installed in versioned subdirectorys, but root requires them to be installed in the non-versioned directorys, and therefore there are links from the nonversioned directory to the versioned one... not at wall... once this is the only problem left I will fix it. we need to add some filter to keep rpmlint happy.
Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
There are init scripts for ROOT daemons in package, but openSUSE 12.3 will provide only systemd. Do you have plan of the migration to systemd? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 11/28/2012 02:15 PM, Dmitry Roshchin wrote:
There are init scripts for ROOT daemons in package, but openSUSE 12.3 will provide only systemd. Do you have plan of the migration to systemd?
Note that systemd will handle SysV init scripts. Migration is nice - but not a requirement, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (4)
-
Alin M Elena
-
Andreas Jaeger
-
Dmitry Roshchin
-
Thomas Zimmermann