I did not think about splitting the BUILD_ROOT's per Python version,
but it seems easy enough to implement and add to the future documentation.
As for the elixir package this should of been closed out as a python-elixir package
already exists in EPEL, It was also brought up at a EPEL #fedora_meeting that dual
packaging is discouraged but never officially denounced.
I would suggest contacting BJ Dierkes regarding the wiki,
he was the individual responsible for implementing multiple_python_os_install_post in to
Python26
and has the most familiarity with said feature.
Jeffrey
On Sep 13, 2011, at 10:48 AM, Toshio Kuratomi wrote:
On Tue, Sep 13, 2011 at 07:50:40AM -0500, Jeffrey Ness wrote:
> Greetings Toshio,
>
> It is possible to byte compile both Python 2.4 and Python 2.6 packages within
> the same SPEC,
> please have a look at bug:
>
>
https://bugzilla.redhat.com/show_bug.cgi?id=700567
>
> The line that is important is "%global __os_install_post
> %__multiple_python_os_install_post"
>
Excellent. That not only works, it simplifies considerably the logic in the
python-pygments package.
One side note when looking at the proposed elixir spec: it's not using
a separate source/build directory for the python26 build. So if there were
things that aren't bytecompiled (because the rpm byte compilation script is
run afterwards) and differ between the python-2.4 and python-2.6 builds
you'd get the wrong thing installed (I'm thinking compiled modules here but
there could be other things as well).
-Toshio "Who now updates the python26 page on the wiki with the recipe for
doing byte compilation"
_______________________________________________
epel-devel-list mailing list
epel-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list
---
Jeffrey Ness
Linux System Engineer
IT Operations [Development]
Rackspace Hosting & IUS Community