On 3/25/20 4:47 PM, Stephen Gallagher wrote:
Starting a new sub-thread.
On Tue, Mar 24, 2020 at 5:33 AM Aleksandra Fedorova <alpha@xxxxxxxxxxxx> wrote:
As Ben is on PTO, I'd like to present the System-Wide Change
https://fedoraproject.org/wiki/Changes/ELN_Buildroot_and_Compose
== Summary ==
The goal of the ELN project is to continuously build Fedora Rawhide
packages and composes in the way which resembles the CentOS and RHEL
build process and to provide a feedback loop for Fedora maintainers on
the status of those builds.
I think we managed to miss a few key points in the Change Proposal
which is directly resulting in a bit of the confusion here.
The first and most important of these is that ELN will *not* be
building the complete Fedora package set. We're going to be building a
selected subset of packages (derived from packages in RHEL 8 and
EPEL). Our current expectation is that we are going to be looking at
fewer than 2500 source packages.We are still working up the initial
list of these and we will update the Change Proposal with it (as well
as providing a fedora-devel post breaking down the known owners).
Second, from this reduced subset, we expect that the overwhelming
majority of the maintainers are Red Hat employees that already work on
RHEL. With this in mind, we think that the level of concern about how
this will affect non-Red Hat contributors is premature. We will reach
out directly to those non-Red Hat contributors we identify.
Finally, of the set of packages that we're going to be including, we
anticipate around 200-300 of them will have distro conditionals that
need investigation (with fewer needing actual modification). The ELN
SIG will be doing this initial investigation and will provide guidance
(and/or PRs) to affected packagers.
Above you indicate that you're looking at fewer than 2500 source
packages, but you expect only 200-300 to have distro conditionals. I
find that rather optimistic that only ~ %10 of the packages will need
conditionals. With such a small initial set, the likelihood is great
that a given package will have at least one missing BuildRequires (there
are no "BuildRecommends" tags to use). Especially since due to the small
package set, a lot of test dependencies will have to be left out.
As others have pointed out, when these conditionals are *required* for
ELN to be built, we can't count on every package maintainer
*voluntarily* agreeing to have them in rawhide. And the added complexity
to maintainers is all too real. If your spec file is used to build 2
builds, good maintainers will feel obligated to make sure any change
doesn't break either of those builds. Which means that they have to know
how ELN works, where it builds and how to test it.
I fully support the proposed solution to have a separate branch, which
can just symbolically point to rawhide if not needed. It's important to
give people a choice.
Tomas
_______________________________________________
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
