Hi,
A package I maintain (mc) has two rarely-used python scripts.
Since they have #!/usr/bin/python header, build machinery automatically adds python dependency.
But I don't want this to happen - the program is very much usable without python too. Requiring python pulls in a top of other stuff which isn't needed.
How can I suppress this in the specfile?
AutoReqProv seems to be a too strong medicine - I would like to blacklist only python dep.
On 07/09/2013 05:26 PM, Denys Vlasenko wrote:
Since they have #!/usr/bin/python header, build machinery automatically adds python dependency.
But I don't want this to happen - the program is very much usable without python too. Requiring python pulls in a top of other stuff which isn't needed.
How can I suppress this in the specfile?
This page should help: http://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering
On 07/09/2013 05:30 PM, Michal Schmidt wrote:
On 07/09/2013 05:26 PM, Denys Vlasenko wrote:
Since they have #!/usr/bin/python header, build machinery automatically adds python dependency.
But I don't want this to happen - the program is very much usable without python too. Requiring python pulls in a top of other stuff which isn't needed.
How can I suppress this in the specfile?
This page should help: http://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering
Thanks, looks like what I needed!
On Tue, Jul 09, 2013 at 05:26:19PM +0200, Denys Vlasenko wrote:
Hi,
A package I maintain (mc) has two rarely-used python scripts.
Since they have #!/usr/bin/python header, build machinery automatically adds python dependency.
But I don't want this to happen - the program is very much usable without python too. Requiring python pulls in a top of other stuff which isn't needed.
Are those scripts installed into /usr/bin ? If so then, IMHO, removing the python dependency is not appropriate, regardless of whether the scripts are used frequently or not. Splitting them out into a sub-RPM might be a more suitable approach.
How can I suppress this in the specfile?
AutoReqProv seems to be a too strong medicine - I would like to blacklist only python dep.
You can filter the provides/requires with a regex:
https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering#Fi...
Daniel
On Tue, Jul 09, 2013 at 04:37:40PM +0100, Daniel P. Berrange wrote:
On Tue, Jul 09, 2013 at 05:26:19PM +0200, Denys Vlasenko wrote:
Hi,
A package I maintain (mc) has two rarely-used python scripts.
Since they have #!/usr/bin/python header, build machinery automatically adds python dependency.
But I don't want this to happen - the program is very much usable without python too. Requiring python pulls in a top of other stuff which isn't needed.
Are those scripts installed into /usr/bin ? If so then, IMHO, removing the python dependency is not appropriate, regardless of whether the scripts are used frequently or not. Splitting them out into a sub-RPM might be a more suitable approach.
<nod> -- If this is a Fedora package, then a subpackage is definitely the way to go. Filtering out a dependency that is actually present would be introducing a bug.
-Toshio
On Tue, Jul 9, 2013 at 12:10 PM, Toshio Kuratomi a.badger@gmail.com wrote:
On Tue, Jul 09, 2013 at 04:37:40PM +0100, Daniel P. Berrange wrote:
On Tue, Jul 09, 2013 at 05:26:19PM +0200, Denys Vlasenko wrote:
Hi,
A package I maintain (mc) has two rarely-used python scripts.
Since they have #!/usr/bin/python header, build machinery automatically adds python dependency.
But I don't want this to happen - the program is very much usable without python too. Requiring python pulls in a top of other stuff which isn't needed.
Are those scripts installed into /usr/bin ? If so then, IMHO, removing the python dependency is not appropriate, regardless of whether the scripts are used frequently or not. Splitting them out into a sub-RPM might be a more suitable approach.
<nod> -- If this is a Fedora package, then a subpackage is definitely the way to go. Filtering out a dependency that is actually present would be introducing a bug.
-Toshio
If you wanted to be a complete weasel, you could use "#!/usr/bin/env python". If the scripts are samples or add-on scripts, not normally deployed, such as the suite of server-side post-comit nad pre-common tools for Subversion, you might dump them in /usr/share/doc/[package]-%{version}/scripts, and turn off the execute bit.
-
Daniel P. Berrange -
Denys Vlasenko -
Michal Schmidt -
Nico Kadel-Garcia -
Toshio Kuratomi