Am 14.12.2015 23:19 schrieb B Watson:
On 12/14/15, Philip Lacroix <[email protected]> wrote:
Am 14.12.2015 21:37 schrieb Brent Earl:
I think that package duplication is unnecessary. An if else
statment
in the SlackBuild would be the solution I think.
Thanks.
I'll either edit my package's README according to your solution and
add
"%README%" to REQUIRES.
What happens if someone needs both python 2 and 3 support?
Does the python3 stuff actually conflict with the python2 stuff? If
not,
maybe it'd be good to allow building both instead of choosing only one
or the other.
This is what some of us have been doing, but as Larry suggested:
(...) I'm also not sure how to handle packages that
put files in /usr/bin directory (like python-pillow) for python2 and
python3 scripts. If python3 files are built after python2 files, then
everything in /usr/bin/* will have a shebang with #!/usr/bin/python3.
I'm
not sure that is a desired outcome.
This is the case for example with python-pillow, which has 13 files in
/usr/bin.
_______________________________________________
SlackBuilds-users mailing list
[email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
