----- Original Message -----
From: "Jason L Tibbitts III" <tibbs(a)math.uh.edu>
To: devel-announce(a)lists.fedoraproject.org
Sent: Tuesday, August 4, 2015 11:34:06 PM
Subject: [Guidelines change] Changes to the packaging guidelines
Here are the recent changes to the packaging guidelines.
-----
The big change is that the Python guidelines have been extensively
reorganized and partially rewritten, and new macros are available which
simplify packaging by removing some of the boilerplate which was
previously required.
The main guideline page has been slimmed down to show the more basic
info and a clean and simple spec using the new macros which is free of
multiline conditionals.
boilerplate previously associated with python packages. Some of the
more esoteric information has been moved to an appendix page to keep the
main page of reasonable size.
The new guidelines are currently only functional on Fedora 22 and newer
releases, but are currently in updates-testing for Fedora 21 and EPEL7.
The older guidelines are preserved in a separate page and we'll try to
keep them updated with new requirements.
The new guidelines page:
*
https://fedoraproject.org/wiki/Packaging:Python
Sorry for late reply.
From the Python packaging:
# Must do the python2 install first because the scripts in /usr/bin are
# overwritten with every setup.py install, and in general we want the
# python3 version to be the default.
%py2_install
%py3_install
I don't think that binaries of python module should be already switched to
the state that non versioned binary is python3 binary.
While /usr/bin/python points to /usr/bin/python2 and python-foo provides python2 version
of the foo package I would expect binary foo to run on python2.
This applies for modules binaries such as pytest (nosetests, pip, ...) where is
difference between running python2 and python3 version of the binary.
Currently we should have non versioned binaries to run on python3 only for python
applications (devassistant) where both python2 and python3 version of the application
provide same functionality.
Therefore I suggest to switch order of pyX_install macros.
The appendix:
*
https://fedoraproject.org/wiki/Packaging:Python_Appendix
The old guidelines:
*
https://fedoraproject.org/wiki/Packaging:Python_Old
Note that these cleaned up pages (and the old copy) include some
new guidelines as well:
There is new section indicating that -OO must not be used for python
versions less than 3.5.
*
https://fedoraproject.org/wiki/Packaging:Python#Optimization
There are requirements for what python module packages must provide
(via Provides:):
*
https://fedoraproject.org/wiki/Packaging:Python#Provides
Related FPC tickets:
*
https://fedorahosted.org/fpc/ticket/281
*
https://fedorahosted.org/fpc/ticket/534
*
https://fedorahosted.org/fpc/ticket/542
*
https://fedorahosted.org/fpc/ticket/545
*
https://fedorahosted.org/fpc/ticket/552
-----
Guidelines have been added covering services which need to perform setup
when they are first started (including self-signed certificate
generation).
*https://fedoraproject.org/wiki/Packaging:Initial_Service_Setup
*https://fedorahosted.org/fpc/ticket/506
-----
The guideline on spec file naming was moved into the main guidelines and
now requires that its name be constructed by taking the name of the
source package and appending ".spec".
*
https://fedoraproject.org/wiki/Packaging:Guidelines#Spec_File_Naming
*
https://fedorahosted.org/fpc/ticket/553
-----
FPC can now grant exceptions to the regular package review procedures.
*
https://fedoraproject.org/wiki/Packaging_Committee#Review_Process_Exempti...
*
https://fedorahosted.org/fpc/ticket/539
*
https://fedorahosted.org/fesco/ticket/1435
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce