[gobolinux-users] Re: Compiling Glibc 2.3.6 (Carlo Calica)

[Hisham Muhammad]

On 5/19/06, =RiCo= <rico.thorn at gmail.com> wrote:
> I am no expert, but i think i might be able to at least make others feel
> smarter if what i have to say is not too clued up :P
>
> If i am correct it is possible to have more than one version of a program
> installed on gobolinux because they have separate folders, so perhaps you
> could check the dependencies of a program being updated and the new version
> and if there is a clash then install the new version separately. Does that
> make sense?

It does, but it's not exactly how it works, because while programs are
stored separately, they have to live together under /System/Links.
When files have different names, such as different versions of
well-behaved libraries, what you described works well. For most
applications, that's not the case. We have ideas/prototypes/unfinished
code that point towards a solution for this problem (a dynamic links
index) but that's still far away from a releasable state. We've got
the plan outlined, but the priority now is to get the new build
environment 'done' and do a new release with it.

> And i do not think the delay on 013 is hurting users, 012 is fully
> functional. I'm looking forward to 013 becuase I assume it will be more
> 'finished' or 'perfected', so a compromise for the sake of time would be
> illogical from my point of veiw. But i do want to know when...

Me too. I for one would like to have a time-based release cycle (just
my personal opinion), but for that we'd have to have a proper "release
cycle", instead of working in disorganized bursts like we do now. The
infrastructure work we're doing (which is delaying 013) is the key to
that, as I see it.

I do want to get 013 out ASAP, but those infastructure changes have
caused many regressions. André told me he committed all missing
changes to BuildLiveCD, so it is up-to-date now.

Updating packages in the CD build environment is still a pain, though,
so that should be the last big change to be made to it. Then we can
focus on testing and building the actual packages from the ISO, I
believe.

There's also the whole hardware detection business, about which I'm
entirely out of the loop -- if anyone has any info on its current
status, let us know.

-- Hisham