Re: Fedora 34 Change: Enable spec file preprocessing (System-Wide Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 18 Dec 2020 at 17:03, clime <clime@xxxxxxxxxxxxxxxxx> wrote:
>
> On Fri, 18 Dec 2020 at 16:23, James Szinger <jszinger@xxxxxxxxx> wrote:
> >
> > On Fri, 18 Dec 2020 00:51:49 +0100
> > clime <clime@xxxxxxxxxxxxxxxxx> wrote:
> >
> > > Well, the users here are still packagers here no? I thought the "User"
> > > in the title means "end user" who shouldn't be affected by it. Maybe
> > > Ben can clarify this.
> >
> > I am making a distinction between Fedora packagers who use the Fedora
> > infrastructure to build RPMs for the Fedora repositories, and second
> > and third party packagers who use their own infrastructure.  External
> > packagers count as ‘users’ for the purposes of change proposals,
> > especially infrastructure changes such as this.  Many change proposals
> > have no effect for external packagers, or have the same effect as for
> > the general user base.  This proposal, however, seems potentially
> > disruptive for external packagers, and I want to see those issues
> > specifically addressed in the change proposal.
> >
> > I will advocate that external packagers are of strategic importance to
> > the Fedora Project.  The software they provide encourages the adoption
> > of Fedora.  They form a pool a potential Fedora packagers.  They are
> > the technical experts that support the local users.  They are
> > fundamental to the Fedora Mission:
> >
> >     Fedora creates an innovative platform for hardware, clouds, and
> >     containers that enables software developers and community members
> >     to build tailored solutions for their users.
> >
> > Supporting external packagers drives the Four Foundations: Freedom,
> > Friends, Features, and First.
>
> I agree the change proposal should address those issues.

I have updated the change description
(https://fedoraproject.org/wiki/Changes/Enable_Spec_File_Preprocessing)
with the feedback I've been given in this thread.

I have also expanded the "User experience" section so that it
addresses the mentioned issues of having spec file templates (i.e.
something which is not understood by rpmbuild) in dist-git instead of
just plain spec files.

Also some links to interesting past discussions about the dynamic
changelog and release generation were added into the description (the
problem actually has a very long history and was discussed many
times).

Hopefully, I didn't forget to mention something (will add it later if I did).

Best regards!
clime

>
> >
> > Jim
> > _______________________________________________
> > 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
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux