On 11 June 2015 at 14:05, Jason L Tibbitts III <tibbs(a)math.uh.edu> wrote:
>>>>> "NC" == Nick Coghlan
<ncoghlan(a)gmail.com> writes:
NC> I agree it doesn't make sense to include that information in the
NC> Python packaging guidelines, but I think it does make sense to
NC> provide such recommendations *somewhere*.
I obviously agree, given that I wrote that I would try and draft
something. Just haven't had much time yet.
Ah, my apologies - I missed that sentence when I read your reply.
NC> Along those lines, it would potentially be useful to have a
Python
NC> specific packaging *tutorial* on the wiki an an alternative to the
NC> generic
https://fedoraproject.org/wiki/How_to_create_an_RPM_package
NC> that assumes folks will be doing everything by hand.
That's certainly not a bad idea. It's a wiki; feel free to run with it.
My own packaging experience is limited enough that I don't consider
myself qualified to provide advice on how best to go about it - my
involvement in Fedora's Python policy development has been from an
upstream perspective rather than a Fedora perspective.
NC> For Python, it would make more sense to start with a tool
like
NC> Slavek's pyp2rpm to generate the initial SPEC file:
NC>
https://pypi.python.org/pypi/pyp2rpm
The problem with doing any of this now is that the python guidelines are
in significant flux and will hopefully emerge in a much cleaner state
with various convenience macros to handle the bulk of the heavy lifting.
Yeah, that makes sense. Once it settles down again and pyp2rpm can be
updated accordingly, then a simpler getting started guide will be
easier to write and maintain.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia