[gobolinux-users] Compile script annoyances

[V]

Hi all,

I've updated to the latest set of scripts and I tried
to Compile xorg and had a few issues.  Here's my
feedback.

1. When the process started it asked if I wanted to
install Zlib 1.2.3, I said 'Y' and it reported back it
was already installed.

The script hung at 100% CPU utilization, I
control-c'ed and it continued.

2. As others have mentioned, I got asked a bunch of
times: Compile: /Programs/Xorg/7.1 already exists.
Continue? [Y/n], and also if I wanted to remove the
existing source folders, etc.

3.  Multiple prompting for the same item

In the Xorg compile, Zlib 1.2.3 was brought up several
times (at least 5, maybe more).  Can we just cache the
result of a users input so if the same question pops
up (even though it theoretically should not if
everything is "kosher") it doesn't hold things up?

4. The automatic dependency system used to update a
Recipe after a compile seems like it's a 95% solution,
but the other 5% is a real problem.

As we have all agreed, Glibc is still listed as a
dependency and this causes all sorts of havoc since
one cannot upgrade Glibc without special voodoo.  So
we need to really remove this as a dependency.

I've also noticed with Compile, since someones Recipe
may have a dependency with a different revision than
the one installed (older or newer), one gets prompted
to answer if this dependency should be installed or
compiled even if you have an acceptable version
installed.

I have KDE 3.5.0 but I've compiled something where the
person who created the recipe had KDE 3.4.3 and I get
prompted if I want to install that version of KDElibs,
etc.  A careless response could jack up the system.

Maybe we should only prompt if the dependency listed
is newer than an installed version.  i.e. you want
Xorg, and you have GLib 1.2.2 and 1.2.3 is listed,
then maybe prompt.

Or perhaps, only prompt if the dependency is not there
and warn the user his version is newer/older than an
existing dependency.  I've noticed that there are
instances where specific versions of something are
required (i.e. you must have Tcl >= 8.2) but in most  
cases it does not matter.  Usually a program's
configure script will tell you if it's an issue.  

Maybe do a test run of configure and grep for
mismatching versions?

Maybe we have profiles for Compile that allow the user
to set how these default conditions are handled?

Another approach of course could be the manual method
(reading the readme or associated documents) and
inserting in the Recipe that version >= x.y.z of
Prog.Z is acceptable (and adding support for this into
the Recipe/Compile system).

Sort of the same issue, the dependencies are sometimes
valid for one persons' configuration but it is not
global.  I think I was trying to compile SDL or an
related SDL library and DirectFB was listed as a
dependency since whomever supplied the Recipe must had
or needed DirectFB.  

This is obviously not a requirement for SDL, and since
something like DirectFB is somewhat specialized, it's
possible if one answers "install everything" it could
fail at that stage.

I don't know what can be done about this since this is
added by an automated process.

Can we create a list of annoyances with the current
set of scripts (if such a list is not already with
someone internally) and try to resolve some of these
outstanding problems?

I really like the Gobo system a lot.  Everytime I pop
back and use another Linux like Gentoo or
Ubuntu/Kubuntu, I find myself wishing for Compile or
InstallPackage since they work pretty well.

But the Gentoo/Ubuntu package management is clever
enough, or perhaps brute force enough that you say
install something, and whatever else needs to be added
is done almost automagically.  Not having to answer
Y/n, or remove/reunpack/etc a hundred times is really
nice.

The current deficiencies in the Gobo system make it
nearly impossible to issue 'Compile prog' and walk
away with high confidence further manual intervention
won't be needed.  This becomes increasing problematic
the more you want or need to do with the system.

As usual I'm verbalizing more criticisms than
accolades of Gobo.  Just want to be clear, I'm
providing my opinions in the spirit of positive
feedback and constructive problem solving.

V.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com