- Append revision numbers in Recipes/Packages version numbers, for reflecting small changes at GoboLinux level, such as Recipes modifications or introduction of new patches.
- Introduce a special directory for package management specific purposes and let packages (or the user) choose under which prefix they will be installed. Currently, GoboLinux package management tools understand that a package 'Foo', version 'VerFoo', is installed if, and only if, there is a directory structure 'Foo/VerFoo' under the directory '/Programs', right? (maybe not completely) But I think there are some classes of packages that don't fit very well in '/Programs', such as packages for additional fonts (that would be placed in '/Files/Fonts') and application add-ons (that could be installed in '/Files/Plugins').
So, my suggestion is to introduce a new directory (e.g.: '/PackageManagement' ) that would be, for management tools, what '/Programs' currently is. This directory could be hidden (by GoboHide), and would be populated as new packages are being installed. I thought in two possible approaches:
a) When a package 'Foo' is installed under '<prefix>', a link to '<prefix>/Foo' is created in '/PM'.
b) When a package 'Foo', version 'VerFoo', is installed under '<prefix>', a directory 'Foo' is created in '/PM' and a link to '<prefix>/Foo/VerFoo' is created in '/PM/Foo'. In this case, when updating the list of available versions in GoboLinux package repositories, links to all of that versions could be created, and the management tools would understand that a given version of package 'Foo' is available, but not actually installed, if the corresponding link under '/PM/Foo' is broken.
I think another approach such that the directories 'Resources' of packages could also be placed under '/PM' would be better, but I'm not sure about it.
What do you think?
_______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
