On Wed, Aug 19, 2020 at 9:12 AM Scott Talbert <swt@xxxxxxxxxx> wrote: > > On Wed, 19 Aug 2020, Christopher wrote: > > > 1. Do I need epel8-playground? I want to keep the task of maintenance > > simple, and I don't want to deal with another branch to think about. I > > don't want choices, as that adds complexity. I want one simple path, > > because packaging is *not* my full time job. > > Under the normal configuration, you don't need to really worry about > epel8-playground, if you don't want to. Whatever you build in epel8 will > automatically be built in epel8-playground also. > > > 2. Can I remove the 'package.cfg' file? Is it needed? Will everything > > work with epel8-testing and going to epel8-stable if this file is > > removed? I'd really like to maintain a single git history, rather than > > two, and the presence of this file seems to interfere with that. > > (Alternatively, if the package.cfg file contained some conditional > > directive, like 'if-branch = epel8', which probably should have been > > the design, in order to support single git history packages like me, > > then I wouldn't mind the file being present in the master/rawhide > > branch, but it doesn't.) > > You can technically remove it. Then, nothing will be built in > epel8-playground automatically. It won't affect epel8. > > Scott So, just to be absolutely clear... I can remove the file, just do epel8 as normal, and completely ignore the epel8-playground branch forever? Can I have the extra commit that added the file removed by force-pushing the prior commit, so it's easier to fast-forward merge my 'master' branch onto epel8 without doing a bunch of crazy git merge nonsense so they have the same HEAD commit? Can I have the epel8-playground branch removed? I never wanted it. I know I can just ignore it and never check it out locally... but... it's going to bug me being there on the remote. Sorry for all the questions. I don't normally care about EPEL, so all this is a bit new to me. Thank you for indulging me. _______________________________________________ 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
