On 24 August 2016 at 02:10, Jason L Tibbitts III <tibbs(a)math.uh.edu> wrote:
>>>>> "PV" == Petr Viktorin
PV> - Make it standard practice in Fedora to use this data and treat the
PV> spec file as an immutable generated artifact.
If you're saying that any changes which are made to the spec file (say,
by release engineering doing a rebuild or by someone tweaking the
package for pretty much any reason) will be overwritten, this is not a
particularly good idea.
I think it's the direction we should be aiming to go, though -
creating snowflake Python packages in a pyp2rpm world should be as
questionable a decision as creating a snowflake server is in an
If a stock standard "dump some files in site-packages, and maybe
install a command line entry point") Python project cannot be
automatically rebased and the spec file regenerated without losing any
data, then that's either a failure to upstream a metadata fix, or else
a problem to be addressed in the spec file generator.
Folks should still have a way to say "this project is a special
snowflake, and I am going to carefully curate the spec file by hand",
but they should also have to opt in to that, rather than having it as
the default (just as all deployed servers should be under
configuration management by default, and people have to turn that off
if they want their local modifications to stick).
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia