[gobolinux-users] Package Manager

[gobolinux at tjconnell.co.uk]

on 8/4/07 10:01 AM, gobolinux-users at lists.gobolinux.org wrote:

> On Sun, 08 Apr 2007 09:49:24 +0200, Tom Connell
> <Gobolinux at tjconnell.co.uk> wrote:
>
> Manager doesn't install dependencies by design, but I know that this fact
> isn't very obvious
> Either we should redesign Manager, perhaps make it use Freshen, or state
> clear that Manager shouldn't be used for system updates.

I think that should be done! A tool that doesnt work is worse than a tool that
doesnt exist!!
>
>> 2) InstallPackage IS resolving dependencies and generating the list and
>> offering an option to install all (ia) this is not happening as only the
>> first (FontConfig) was installed before I was returned to a prompt!
>>
> Do you get any error messages before returned to the prompt? There was a
> bug in Scripts when there were new settings for an application that made
> InstallPackage to drop all dependencies it should install after the app
> with the new settings.

No error, but I did see a new settings message so maybe this bug is still
present
Cant say what version of Scripts I am using as my system will not boot again
(see separate thread), but it was the first thing I updated (Using Manager so
maybe not right!!!!) after installing from Live CD
>
>> 3) I started to install the dependencies individually and hit a wall at
>> GCC 4.1.2 which failed verification! (Why does a binary package like
>> Firefox NEED GCC?)
>>
> As Michael said, you can force installation when verification fails, by
> calling SymlinkProgram manually. However no app should fail. What version
> of scripts do you use?
>
Cant say what version of Scripts I am using as my system will not boot again
(see separate thread), but it was the first thing I updated (Using Manager so
maybe not right!!!!) after installing from Live CD. Cant try symlinking GCC
either

> That some binary apps need GCC isn't because it needs to build something,
> but because it is dynamically linked against libraries in the GCC package.
>
OK, Just seems odd!

>> The dependency list in the info box in Manager is colour coded! What do
>> these colours mean  as I can find no help??
>>
> I believe that the colors represent the media available for installation
> of that dependency, when the dependency is not installed. Blue is recipe,
> light green is official package, dark green is contributed package and red
> means that no mean to install the dependency is found. The dependency is
> black when fulfilled. However, I can see that the parsing of the versions
> isn't accurate as I get several dependencies color coded as they weren't
> installed when I have a version installed that fulfills the dependency.
> Most probably a bug.
>
>> I assumed a red version means it is needed! However the colours don't
>> change after the required dependancy is installed??
>>
> Any color besides black means that Manager can't satisfy that dependency.
> Red means that no means to install the dependency is found. However, as I
> said, it seems like Manager have problem parsing the versions.
>
>> The version is also displayed in blue and some program names are also in
>> red???
>>
OK, Some documentation would be nice, but better still a working Manager

Thanks for help so far see new thread for my latest problem.

Tom Connell