> @DimStar77 ,
>
> > Just to chime in here as well: openSUSE has the 'distro bootstrap' split
> > and tries to keep it under control. It's right that python3 is already in
> > that chain (we build python3 is a minimal set with as few deps as possible,
> > and an enhanced set, in two runs)
>
> I am curious, what depends on it apart from glibc (I guess)?
so far, glibc is the only python3(base) consumer (and I was not happy when the
started - but our arguments were dismissed by the glibc maintainers back then
too)
> > meson
>
> If you have Python, no other deps.
Yep.. that does not sound scary (as long as one does not care for meson's test
suite!)
> > ninja
>
> Easy-peasy, C++.
'almost is everything turns out to be easy' - yet, one also wants to keep it
small to get a bootstrap cycle.
> > re2c
>
> Technically this is optional since ninja ships pre-generated sources.
Definitively not what we aim for. vendored-in sources is the wrong solution to
any problem. For the same reason as most distros stopped linking everything
statically.
Preferably, the goal is to eliminate something out of the ring for something
else coming in. That would be the optimal case. The more there is in the
bootstrap cycle, the worse it gets on ABI changs if you take care of a distro
that's is self-contained
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1209#issuecomment-625912336
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
