Kevin Fenzi wrote:
> I'm not sure how to handle the dychomoty between having different spec
> files for each release and wanting to maintain just one spec that has a
> bunch of crazy conditionals in it. Even thought I do this too, I think
> we need a workflow that discourages this somehow.
I don't see what's wrong about the conditionals. Usually, the packages just
work across releases with few to no conditionals. Occasionally, there is a
conditional. It is still usually not worth letting the branches diverge. I
only maintain different specfiles per branch if I actually want to ship
different versions of the upstream software there.
And also, is the fancy Modularity everyone except me is so excited about not
actually about moving towards the one specfile for all Fedora releases
model, among other things? But of course, the shared specfile can also
easily be done without Modularity, with fast-forward merges as it has always
been done.
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
