[opensuse-packaging] What do I do with a package that contains only development files?
Hi, I've created a package home:plater/lv2core which contains doxygen docs, only one binary lv2config, lv2.h, lv2.ttl, manifest.ttl and lv2core.pc. I'm not really sure what the ttl files are for but the package is necessary for new package slv2 to build and that is it's only purpose. IMHO everything should be in one package but rpmlint doesn't like such things so I've put everything except lv2config in the main package and the rest in the devel package. I also get an rpmlint warning stating that the main package should be noarch, lv2config is a python script. Am I doing the right thing? Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le vendredi 14 janvier 2011, à 19:37 +0200, Dave Plater a écrit :
Hi, I've created a package home:plater/lv2core which contains doxygen docs, only one binary lv2config, lv2.h, lv2.ttl, manifest.ttl and lv2core.pc. I'm not really sure what the ttl files are for but the package is necessary for new package slv2 to build and that is it's only purpose. IMHO everything should be in one package but rpmlint doesn't like such things so I've put everything except lv2config in the main package and the rest in the devel package. I also get an rpmlint warning stating that the main package should be noarch, lv2config is a python script. Am I doing the right thing?
It sometimes makes sense to have everything in a package, without a devel package. See orc for an example (well, it does have subpackages, but not a devel one). So if you're sure it's right, just do it the way you orginally did it; rpmlint cannot detect those cases automatically. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 01/14/2011 08:15 PM, Vincent Untz wrote:
Le vendredi 14 janvier 2011, à 19:37 +0200, Dave Plater a écrit :
Hi, I've created a package home:plater/lv2core which contains doxygen docs, only one binary lv2config, lv2.h, lv2.ttl, manifest.ttl and lv2core.pc. I'm not really sure what the ttl files are for but the package is necessary for new package slv2 to build and that is it's only purpose. IMHO everything should be in one package but rpmlint doesn't like such things so I've put everything except lv2config in the main package and the rest in the devel package. I also get an rpmlint warning stating that the main package should be noarch, lv2config is a python script. Am I doing the right thing?
It sometimes makes sense to have everything in a package, without a devel package. See orc for an example (well, it does have subpackages, but not a devel one).
So if you're sure it's right, just do it the way you orginally did it; rpmlint cannot detect those cases automatically.
Vincent
It's not going further than multimedia:libs atm, it's to give ardour LV2 support, requested by a user. So until a package in the main distribution needs it, I'll leave it as it is. Have you ever seen rpmlint doing this? : lv2core-devel.x86_64: W: non-standard-group Development/Libraries/C?and?C++ from : Group: Development/Libraries/C and C++ Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le vendredi 14 janvier 2011, à 20:41 +0200, Dave Plater a écrit :
It's not going further than multimedia:libs atm, it's to give ardour LV2 support, requested by a user. So until a package in the main distribution needs it, I'll leave it as it is.
Better to fix it now, while you think about it, imho ;-) But it's up to you.
Have you ever seen rpmlint doing this? : lv2core-devel.x86_64: W: non-standard-group Development/Libraries/C?and?C++ from : Group: Development/Libraries/C and C++
Try to replace what looks like spaces with space. You might have non-breaking spaces, or something similar. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2011-01-14 19:15:10 +0100, Vincent Untz wrote:
Le vendredi 14 janvier 2011, à 19:37 +0200, Dave Plater a écrit :
Hi, I've created a package home:plater/lv2core which contains doxygen docs, only one binary lv2config, lv2.h, lv2.ttl, manifest.ttl and lv2core.pc. I'm not really sure what the ttl files are for but the package is necessary for new package slv2 to build and that is it's only purpose. IMHO everything should be in one package but rpmlint doesn't like such things so I've put everything except lv2config in the main package and the rest in the devel package. I also get an rpmlint warning stating that the main package should be noarch, lv2config is a python script. Am I doing the right thing?
It sometimes makes sense to have everything in a package, without a devel package. See orc for an example (well, it does have subpackages, but not a devel one).
So if you're sure it's right, just do it the way you orginally did it; rpmlint cannot detect those cases automatically.
though... i would add a: Provides: lv2core-devel = %{version}-%{release} and use the lv2core-devel in the other packages as buildrequires. so when the package gets some shared library at some point, you dont have to change anything. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 01/17/2011 01:19 PM, Marcus Rueckert wrote:
On 2011-01-14 19:15:10 +0100, Vincent Untz wrote:
Le vendredi 14 janvier 2011, à 19:37 +0200, Dave Plater a écrit :
Hi, I've created a package home:plater/lv2core which contains doxygen docs, only one binary lv2config, lv2.h, lv2.ttl, manifest.ttl and lv2core.pc. I'm not really sure what the ttl files are for but the package is necessary for new package slv2 to build and that is it's only purpose. IMHO everything should be in one package but rpmlint doesn't like such things so I've put everything except lv2config in the main package and the rest in the devel package. I also get an rpmlint warning stating that the main package should be noarch, lv2config is a python script. Am I doing the right thing?
It sometimes makes sense to have everything in a package, without a devel package. See orc for an example (well, it does have subpackages, but not a devel one).
So if you're sure it's right, just do it the way you orginally did it; rpmlint cannot detect those cases automatically.
though... i would add a:
Provides: lv2core-devel = %{version}-%{release}
and use the lv2core-devel in the other packages as buildrequires. so when the package gets some shared library at some point, you dont have to change anything.
darix
Packman provides lv2core and lv2core-devel and by coincidence I've provided the same packages so I'm going to stick with that layout. A further complication is the binary in the lv2core rpm lv2config needs redland python bindings which I've built within the redland package and am still checking before submission. So multimedia:apps ardour has LV2 support and the user is happy. The slv2 packages and lv2core-devel enable ardour to build with LV2 plugin support and I've removed the manual requirement of lv2core for redland-python untill redland-python exists in factory. lv2config doesn't work with the initial redland-python bindings rpm installed atm. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, 14 Jan 2011, Dave Plater wrote:
Hi, I've created a package home:plater/lv2core which contains doxygen docs, only one binary lv2config, lv2.h, lv2.ttl, manifest.ttl and lv2core.pc. I'm not really sure what the ttl files are for but the package is necessary for new package slv2 to build and that is it's only purpose. IMHO everything should be in one package but rpmlint doesn't like such things so I've put everything except lv2config in the main package and the rest in the devel package. I also get an rpmlint warning stating that the main package should be noarch, lv2config is a python script. Am I doing the right thing?
You can also make the main package empty and only build a -devel
package. Much like for example gmp and mpfr handle this
(though they also have a shared library sub-package).
Richard.
--
Richard Guenther
participants (4)
-
Dave Plater -
Marcus Rueckert -
Richard Guenther -
Vincent Untz