Re: Introducing Square 1

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

 



On Mon, Oct 28, 2019 at 2:58 PM Peter Robinson <pbrobinson@xxxxxxxxx> wrote:
>
> On Mon, Oct 28, 2019 at 8:00 PM Troy Dawson <tdawson@xxxxxxxxxx> wrote:
> >
> > I would like to introduce a plan I call Square 1 [1][2]
> >
> > There are two goals to Square 1.
> > The first is to get, and keep, the core buildroot[3] packages, self-hosting[4].
> > The second is to get the list of core buildroot packages as small as possible.
>
> Why can't this be done as part of the minimisation objective? To have
> yet another project with another name and another focus and set of
> tools just appears to be a little bizarre
>

I'd love for it to fold into the Minimization project.
That project has a better name, and Adam is much more familiar with
getting things done properly in Fedora.
Currently, the Minimization project is geared towards only binaries,
and not the source dependencies.  It is still getting setup and on
it's feet.  I'm worried that throwing source and dependency tree's at
it will knock it down before Minimizations infrastructure is in place.

But, I'm looking at when we need to get started for RHEL9, and I've
seen how slow things can take when dealing with Fedora dependencies,
and it has me concerned.  I'd like to get the discussion started now,
so hopefully we have some things figured out and possibly working by
the time it is needed.

Is the name confusing?  Yep.  But Square1 is all I could think of at the time.
Can/Should this be merged into Minimization?  Yes, that is my hope.
Or, at least a good part of it get's merged in there.  Eventually.

> > What are the benefits to Square 1?
> > More stable release and less failed builds.
> > If we are able to shrink binaries, faster koji builds.
> > Smoother initial creation of RHEL 9.[5]
> >
> > What are the milestones to get these benefits?
> > - Get initial list of "core binaries"
> > - write/find software that will find binary/source dependencies

I've been looking at the dnf plugins, specifically builddep.
If we can get that to be recursive, that would help tremendously.

Looking at the plugins, we should also be able to help the
Minimization project get their list of packages in a usable format.
Currently they are installing all their packages (I believe in a
container), and then grabbing the rpm database from that.  I think we
should be able to make a plugin that generates the list of packages
that would be installed, and instead of installing them, generates an
repo and/or rpm database.

> > - write/find software that will track binary/source dependencies
> > - write/find/setup automation that finds and tracks binary/source
> > dependencies, so people can easily see what has changed over time.
> > - work with package maintainers to trim down binary/source dependencies
> > -- trimming out "extra" package languages.  (ex: perl for a
> > minor script, when everything is in python.)
> > -- trimming functionality and/or moving functionality to sub-packages
> > or separate package.
> > - integrate these tests into the rawhide gating system, to alert when
> > new dependencies have been added.
> >
> > Much of this work overlaps with the Fedora Minimization efforts.[6]
> > Square 1 hopes to utilize, rather than duplicate, their efforts.  And
> > maybe some tools created for Square 1 can help the minimization
> > efforts.
> >
> > Thoughts?
> > Ideas?
> > Comments?
> >
> > Troy Dawson
> >
> > [1] - Square 1 is at the heart of Ring Zero
> > [2] - This has nothing to do with the company or software with a
> > similar sounding name.
> > [3] - The core buildroot is the packages in @buildsys-build, and
> > everything needed to build those packages.
> > [4] - self-hosting is the ability to build all the packages on themselves.
> > [5] - Yep, I said it.  We're already looking at RHEL 9.
> > [6] - https://docs.fedoraproject.org/en-US/minimization/
_______________________________________________
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