Re: Fedora 33 System-Wide Change Proposal: ELN Buildroot and Compose V2

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

 



On Mon, Mar 30, 2020 at 01:57:22PM +0200, Miro Hrončok wrote:
> On 30. 03. 20 13:52, Petr Pisar wrote:
> > If I undeestand the proposal correctly there there will be an ELN branch or
> > a name space. But not by default. Only for those packages that reject the
> > change in Fedora.
> 
> I wonder where is this coming from, because that's exactly what we want and
> exactly what the change owners don't want.
> 
That's my impression from Alexandra's replies. I think she wrote that packages
that must significantly differ from Fedora will have an ELN override. So
I conclude their sources must be somewhere stored. And since Koji does not
allow building from a non-dist-git, It must be in the dist-git.

I frankly cannot see how the create-a-pull-request-and-wait-for-the-merge
procedure would scale if the ELN maintainer would need to adjust more than
a few packages.

The easiest way would be probably allow building ELN from pull-requests. But
the maintainability would be terrible.

-- Petr

Attachment: signature.asc
Description: PGP signature

_______________________________________________
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