[opensuse-packaging] Dependency generators in rpm-4.9.0 and rpm dependencies
Hi all, first of all big thanks to mls for rpm 4.9. I've a question about the dependency generators introduced in rpm 4.9 - I want to reuse the Fedora maven.attr and maven.prov they added into jpackage-utils. It will add the maven styled provides into maven packages, so on the end all maven packages can have cross-distro compatible names. There's a problem I see with their approach. The maven.prov is written in Python, that means you have to handle this as dependency somehow. I thought about few ways, but noone seems to me like a good way 1.) add a Requires: python into jpackage-utils, so you have to have python with every java package, because j-u is needed for every JVM we have 2.) move those files into maven package and let it Require python - this is not much far from the 1.) 3.) add BuildRequires: python into every package have BuildRequires: maven - this seems as the best one, even it is confusing for packagers What's your opinion? Regards Michal Vyskocil
Am Dienstag, 31. Mai 2011 schrieb Michal Vyskocil:
Hi all,
first of all big thanks to mls for rpm 4.9.
I've a question about the dependency generators introduced in rpm 4.9 - I want to reuse the Fedora maven.attr and maven.prov they added into jpackage-utils. It will add the maven styled provides into maven packages, so on the end all maven packages can have cross-distro compatible names.
There's a problem I see with their approach. The maven.prov is written in Python, that means you have to handle this as dependency somehow. I thought about few ways, but noone seems to me like a good way
1.) add a Requires: python into jpackage-utils, so you have to have python with every java package, because j-u is needed for every JVM we have 2.) move those files into maven package and let it Require python - this is not much far from the 1.) 3.) add BuildRequires: python into every package have BuildRequires: maven - this seems as the best one, even it is confusing for packagers
What's your opinion?
Usually this is solved by having a maven-devel that serves as "require python and maven.attr" place holder. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Tue, May 31, 2011 at 11:51:25AM +0200, Stephan Kulow wrote:
Am Dienstag, 31. Mai 2011 schrieb Michal Vyskocil:
Hi all,
first of all big thanks to mls for rpm 4.9.
I've a question about the dependency generators introduced in rpm 4.9 - I want to reuse the Fedora maven.attr and maven.prov they added into jpackage-utils. It will add the maven styled provides into maven packages, so on the end all maven packages can have cross-distro compatible names.
There's a problem I see with their approach. The maven.prov is written in Python, that means you have to handle this as dependency somehow. I thought about few ways, but noone seems to me like a good way
1.) add a Requires: python into jpackage-utils, so you have to have python with every java package, because j-u is needed for every JVM we have 2.) move those files into maven package and let it Require python - this is not much far from the 1.) 3.) add BuildRequires: python into every package have BuildRequires: maven - this seems as the best one, even it is confusing for packagers
What's your opinion?
Usually this is solved by having a maven-devel that serves as "require python and maven.attr" place holder.
Yes, that might works. I'll check that with Fedora guys. Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (2)
-
Michal Vyskocil -
Stephan Kulow