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
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
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
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
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.
On Tue, Jul 9, 2013 at 12:10 PM, Toshio Kuratomi a.bad...@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
