Hello GoboFolks, Just a somewhat brief question this time.
- Is there a way in GoboLinux, a script or some standard, to know what specific "Gobo" name a particular input program name will have? To give you a specific example, take the program called "gst-plugins-base", with the following recent URL: http://ftp.gnome.org/pub/GNOME/sources/gst-plugins-base/1.12/gst-plugins-base-1.12.2.tar.xz I picked the following old recipe here as example by Lucas from +10 years ago, see at the bottom of the list on that URL: http://recipes.gobolinux.org/r/?list=GST-Plugins-Base&ver=0.10.9-r2&file=Recipe You can see that the name is "GST-Plugins-Base". So in the above, something that could, e. g. turn the input String: "gst-plugins-base-1.12.2.tar.xz" into the corresponding name on GoboLinux, being: "GST-Plugins-Base-1.12.2" (You can ignore the version number; I am only interest in the "translated" GoboLinux program name there.) The reason why I ask specifically is because in my ruby cookbooks project, I keep track of programs in yaml files (with the .yml "extension" name). Therein I use a simpler scheme, which is the downcased input, and all '-' and '_' removed, as starting name. So for example, the above would be a local file called "gstpluginsbase.yml". Other scripts can then turn this into the "proper" name, in particular the one that can be used by a configure script via, for example, ./configure --prefix=/Programs/Gstpluginsbase/1.12.2 or ideally, with the GoboLinux naming scheme, then being: ./configure --prefix=/Programs/GST-Plugins-Base/1.12.2 That is the primary reason why I would like to know if there is a script already existing; or a standard that one could read or se. Even if neither one exists, I can write a script that can scan the (remote or local) GoboLinux recipes and automatically add a hardcoded entry towards each local .yml files that I have - but of course, a standard for the naming convention, or an existing script, may be easier to re-use (or perhaps re-implement for me in ruby). When I have this, I think that I will also be able to eventually auto-generate all recent, aka modern, GoboLinux recipes eventually (I am already tracking 3009 programs so far and adding new entries is quite easy; I'll start with auto-generating the simpler GoboLinux recipes, but this may still take a while. On a side note, I also finally have a spare computer and a spare ethernet cable, so I think I can eventually get GoboLinux running on a second machine. The primary one is keeping slackware mostly as a tinker OS). Hope I could explain why I may consider this useful. Cheers! :)
_______________________________________________ gobolinux-users mailing list gobolinux-users@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
