Dear fedora-python-devel,
I noticed a problem with pyp2rpm tool: it's a great tool, but it's hardly visible and new python packager can easily miss it. The fact that both Packaging:Python and SIGs/Python wikipages doesn't properly mention it doesn't really help as well. No fried of mine who recently started working on packaging his project is aware of this tool and I find out about it only because I had weird newcomer's kind of questions on this mailing list and people here were kind enough to point out that I should check it first.
Initially I tried to kind of fix this issue by adding a line about this tool into SIGs/Python page some time ago:
https://fedoraproject.org/w/index.php?title=SIGs%2FPython&diff=418064&am...
The problem is that this doesn't really solve anything. Now I rather feel that more changes are required.
My current idea how to maintain rpm packages for my own python project is summed up here:
https://fedoraproject.org/wiki/User:Marbu/PythonPackaging
Note that this is not a suggestion how the better description should look like. I link it here so that you can point out which part you disagree with (I'm not even a python sig member after all), so that we can catch possible disagreements as soon as possible. My suggestions below assumes that this makes sense. Keep in mind that I have hardly any real experience with python rpm packaging.
So what exactly I have in mind? Compare this page:
https://fedoraproject.org/wiki/Packaging:Python
with:
https://en.opensuse.org/openSUSE:Packaging_Python
The difference includes:
* fedora Packaging:Python page is a packaging policy, which doesn't mention pyp2rpm at all * openSUSE:Packaging_Python page is more like a step by step intro, which includes a clean example how to use SUSE's py2pack tool
See also:
https://fedoraproject.org/wiki/Packaging:Haskell
which clearly points out to cabal-rpm tool right in the beginning.
So my suggestions are:
1) Since the Packaging:Python page is the most visible, I would include quick intro about pyp2rpm as the first section here. 2) Mention Python SIG page here as well. 3) A beginner friendly howto with more details could be maintained separately linked from (or included in) revamped Python SIG page's "Packaging Quickstart" section.
Moreover: I think that it would make sense to link older versions of the guidelines which are valid for epel 6 and 7 like ruby does here:
https://fedoraproject.org/wiki/Packaging:Ruby
I could help me with this feature request:
https://github.com/fedora-python/pyp2rpm/issues/25
Thanks for the feedback.
On 9 February 2016 at 11:13, Martin Bukatovic martin.bukatovic@gmail.com wrote:
Dear fedora-python-devel,
I noticed a problem with pyp2rpm tool: it's a great tool, but it's hardly visible and new python packager can easily miss it. The fact that both Packaging:Python and SIGs/Python wikipages doesn't properly mention it doesn't really help as well. No fried of mine who recently started working on packaging his project is aware of this tool and I find out about it only because I had weird newcomer's kind of questions on this mailing list and people here were kind enough to point out that I should check it first.
I don't have a lot of concrete feedback to offer, since I agree with your description of the problem, and think your proposed tweaks would be a good way of improving things.
As an additional bit of background, there's also https://github.com/developer-portal/content/issues/61 which proposes tweaking https://developer.fedoraproject.org/deployment/rpm/about.html to provide pointers to language specific tools.
Cheers, Nick.
On Tue, Feb 09, 2016 at 05:49:18PM +1000, Nick Coghlan wrote:
I don't have a lot of concrete feedback to offer, since I agree with your description of the problem, and think your proposed tweaks would be a good way of improving things.
Thanks for checking my proposal.
As an additional bit of background, there's also https://github.com/developer-portal/content/issues/61 which proposes tweaking https://developer.fedoraproject.org/deployment/rpm/about.html to provide pointers to language specific tools.
I agree. That's a very good idea, just general introduction of this concept and list of tools would have a great value for a newcomer.
----- Original Message -----
From: "Martin Bukatovic" martin.bukatovic@gmail.com To: python-devel@lists.fedoraproject.org Sent: Tuesday, February 9, 2016 2:13:59 AM Subject: visibility of pyp2rpm tool
Dear fedora-python-devel,
I noticed a problem with pyp2rpm tool: it's a great tool, but it's hardly visible and new python packager can easily miss it. The fact that both Packaging:Python and SIGs/Python wikipages doesn't properly mention it doesn't really help as well. No fried of mine who recently started working on packaging his project is aware of this tool and I find out about it only because I had weird newcomer's kind of questions on this mailing list and people here were kind enough to point out that I should check it first.
Initially I tried to kind of fix this issue by adding a line about this tool into SIGs/Python page some time ago:
https://fedoraproject.org/w/index.php?title=SIGs%2FPython&diff=418064&am...
The problem is that this doesn't really solve anything. Now I rather feel that more changes are required.
My current idea how to maintain rpm packages for my own python project is summed up here:
https://fedoraproject.org/wiki/User:Marbu/PythonPackaging
Note that this is not a suggestion how the better description should look like. I link it here so that you can point out which part you disagree with (I'm not even a python sig member after all), so that we can catch possible disagreements as soon as possible. My suggestions below assumes that this makes sense. Keep in mind that I have hardly any real experience with python rpm packaging.
So what exactly I have in mind? Compare this page:
https://fedoraproject.org/wiki/Packaging:Python
with:
https://en.opensuse.org/openSUSE:Packaging_Python
The difference includes:
- fedora Packaging:Python page is a packaging policy, which doesn't mention pyp2rpm at all
- openSUSE:Packaging_Python page is more like a step by step intro, which includes a clean example how to use SUSE's py2pack tool
See also:
https://fedoraproject.org/wiki/Packaging:Haskell
which clearly points out to cabal-rpm tool right in the beginning.
So my suggestions are:
- Since the Packaging:Python page is the most visible, I would include
quick intro about pyp2rpm as the first section here. 2) Mention Python SIG page here as well. 3) A beginner friendly howto with more details could be maintained separately linked from (or included in) revamped Python SIG page's "Packaging Quickstart" section.
Moreover: I think that it would make sense to link older versions of the guidelines which are valid for epel 6 and 7 like ruby does here:
https://fedoraproject.org/wiki/Packaging:Ruby
I could help me with this feature request:
https://github.com/fedora-python/pyp2rpm/issues/25
Thanks for the feedback.
Hi Martin, I like your ideas, the best way to move this forward is to open a ticket for fpc[0].
[0]https://fedorahosted.org/fpc/
-- Martin Bukatovic _______________________________________________ python-devel mailing list python-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject....
-- Robert Kuska {rkuska}
On Wed, Feb 10, 2016 at 03:52:06AM -0500, Robert Kuska wrote:
Hi Martin, I like your ideas, the best way to move this forward is to open a ticket for fpc[0].
Ah, thanks for pointing this out. The ticket is here:
https://fedorahosted.org/fpc/ticket/598
python-devel@lists.fedoraproject.org