[gobolinux-users] Re: Compiling Glibc 2.3.6

[Hisham Muhammad]

On 5/13/06, Sean E. Russell <gobo at ser1.net> wrote:
> On Saturday 13 May 2006 00:17, Carlo Calica wrote:
> > I see the situation as a compromise between a "version mix n match"
> > and "managed, QA'd deployment".
>
> By managed, you mean bundled system upgrades?

Lots of interesting stuff in this thread, but I don't think I have
much to add to the specific Glibc discussion right now, so I'll be
just adding a comment on this specific topic above.

One thing we *don't* have right now but that I see as a kind of
solution for these stability problems is to do the following:
- treat the recipe store as simply a "pool" of recipes (any version of
anything can go there);
- have lists of recipe/package versions that are known to work well
together; like a "stable" list.

That's just doing what other distros do, of course. There's no need to
reinvent the wheel in terms of distro maintenance (we have a lot of
other wheels to reinvent, so let's not focus on the wrong ones :) ).
What I have in mind is a model with pool+stable list for managed
system upgrades, and the recipe pool split in core/extras for recipes
with assigned maintainers and one-off contributions -- abusing a
little both Debian and Fedora terminologies.

There could be even many of those lists, kind of like some developers'
personal "patch sets" for the Linux kernel. Users who want to follow
one of these lists would use some script to keep their systems in sync
with that list (that script could interact with InstallPackage and
with Compile (to rebuild the user's personal additions to the list,
when needed, etc -- over time the sync script could become very
smart)).

-- Hisham