Thanks, I was convinced this (link based) approach is perfect for
gobo...but the lack of response was worrying me :) ...I will document
the details on the wiki and send out a link...then if everyone is in
agreement we can work out a plan of introducing it into gobo scripts.
would appreciate some more experienced members hisham, carlo,lucas also
giving their inputs...
/System/
Links/
Dependencies/
Glibc/
Current/ (version independent like USE flag
dependencies)
GTK -> /System/Links/USE/GTK
>= 2.4/
ALSA-Lib-1.0.13 ->
/Programs/ALSA-Lib/1.0.13
<= 2.4/
XYZ-1.3.3 -> /Programs/XYZ/1.3.3
USE/
GTK/
ALSA-Lib-1.0.13 ->
/Programs/ALSA-Lib/1.0.13
XYZ-1.3.3 ->
/Programs/XYZ/1.3.3
This should eliminate having to parse through dependency or even USE
files ....
All Remove Program has to do is to check in this folder for dependencies
before uninstalling a program...Also if a program like glibc is forcibly
removed these links just go bad....and a RemoveBroken (force option) can
remove the broken links...
Thanks,
Anshuman
MLA-Gobo wrote:
> On Sunday 01 July 2007 18:19, [EMAIL PROTECTED] wrote:
>
>> This is done through a system wide folder:
>> /System/Links/Dependencies
>>
> *SNIP* <APPLAUSE> Bravo! I like this solution! It seems very Gobo-ish to
> me.
> :Peter
> _______________________________________________
> gobolinux-devel mailing list
> gobolinux-devel@lists.gobolinux.org
> http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
>
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
