----- Original Message -----
On 12/10/2014 03:48 AM, Bohuslav Kabrda wrote:
> Hi all,
> I know I've been promising this for quite some time to several people, so I
> finally managed to put together a proposal for packaging Python 3 in EPEL
> 7 (it'd also scale to EPEL 6 for that matter).
> I've created a wiki page  with the proposal and I'd like to hear
> comments and thoughts on it. There are some TODOs and variants in few
> places - I'd like to hear your opinions on these, or perhaps suggestions
> on better approaches.
> I'll create new documents with the updated proposal at some points during
> the discussion, so that people can easily see where the proposal is going
> without having to compare wiki revisions.
> Is there any other list/interested parties that should be put in CC of this
> mail? If so, please feel free to respond and do that yourself.
Nice to see some progress on this. Some comments:
- We should have /usr/bin/python3, if only for end user convenience.
Yeah, I agree we should have it, although for use in RPMs, I'd suggest discouraging it
and instead promote usage of /usr/bin/pythonXY.
- I want to be able to build my EPEL python3X packages out of my
python dist-git packages' epel7 branch.
Ok, it's not my preference, I'd rather use the third option outlined in the
original proposal (e.g. have separate repos for EPEL python3 packages) because of some of
the downsides I see when using epel-7 branches in standard python dist-git repos. But then
again, that's just my preference and if more people voice the same opinion as you,
I'm fine doing it your way.
Thanks for your comments,
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 http://www.nwra.com
epel-devel mailing list