On Thursday, December 17, 2020 8:05:40 PM CET Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing > > == Summary == > This change should enable an opt-in spec file preprocessor in Fedora > infrastructure for the benefit of packagers. The preprocessor allows > some very neat tricks that were impossible before, for example > generate changelog and release automatically from git metadata or pack > the entire dist-git repository into an rpm-source tarball (effectively > allowing unpacked repos to live in DistGit). It would be nice to see this in some concrete example. E.g. in some 'private-rpkg-preview' branch in some of the existing Fedora packages, so we can make a clearer idea about what this causes with real spec file readability (diff) and the initial newcomer barrier. So we could e.g. checkout that branch, and try to build the package. And see the real pros/cons. > == Benefit to Fedora == > > This change offers solution to some long-standing issues in Fedora > around packaging (i.e. automatic release and changelog generation) I personally wouldn't overestimate these issues, at least according to the questionnaire I tried to do some time ago [1, 2] not many maintainers were interested in the problem to even vote (and I was not surprised). These problems have trivial work-arounds/solutions, discussed in [1]. > while also offering some interesting future options (for example > unpacked dist-git repos). I think that it would be good to consider tito as alternative, when we speak about binding spec with git-archive feature. Do you think it would be possible to allow tito in future? There's also some Packit-team feature named source-git, is this related? - Honestly, in general, I don't like tito, and I don't like rpkg much more. Both are probably better for upstream development and release processes (tito is more standard and convenient IMO) than some custom scripting. But people need to know deeply the use-cases (and even implementation) to compare. Also note that we used to have problems [IIRC 3, 4] in Copr builds from Fedora DistGit -- as the '{{{' syntax collided with some of the existing packages. I view this proposal as a risk that the spec files will look a bit more weird, and the spec files maintenance will start diverging too much. Everything happening for an overestimated triviality as IMO the release/changelog is [1]. [1] https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/2G6OSOSM76O2V6K4COIE2QHNXIBSXPFR/ [2] https://docs.google.com/forms/d/183dSFIN-i9rauEZ0_gtDia7dzkeX-hzfX0ncpqFMYxw/edit#responses [3] https://pagure.io/copr/copr/issue/798 [4] https://pagure.io/copr/copr/issue/1219 Pavel _______________________________________________ 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
