On 8/29/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
On Tue, 29 Aug 2006 11:26:35 +0200, Jonatan Liljedahl <[EMAIL PROTECTED]>
wrote:
> André Detsch wrote:
>> On 8/27/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
>>> I'm thinking of creating a wrapper script for Compile and
>>> InstallPackage
>>> so that one only has to gie one command to install an app. The
>>> application
>>> should be installed from recipe or from package depending on settings
>>> in a
>>> configuration file. This could later be used to update an app to the
>>> latest available version and maybe system wide updates. A bit like
>>> Manager, but for the prompt. Perhaps the script could wrap tools like
>>> DisableProgram and SymlinkProgram as well?
> ...
>
> I think it would be nice also with a cmdline option to choose source or
> binary. And/or even an interactive question: "Foo 1.0 is available in
> [S]ource and as a [B]inary package. Choose one:"
>
Yes, the behaviour should be totally configurable using primarily a file.
For example, I would set it to use recipes if the recipe and package
versions are the same or when the recipe version is later. Is the package
version later, the tool should present the recipe and package versions and
ask me which I want to use.
Some other users might want the binaries most of the times and should have
it the other way around. There should be an option to have it to always
ask and so on. One should also be able to change the default behaviour set
in the conf file using command line options, for instance when one knows
what alternatives there exist and one already knows that one wants to
install the recipe (or package).
>>> My question is: what should it be called?
>>> git - GoboLinux Install Tool or perhaps gpm - GoboLinux Program
>>> Manager?
>>
>> Probably not good options, since they already being used by other
>> programs...
>> I don't have a good suggestion right now :-/
>
> gtb - gobolinux tool box, gobotool, or maybe even just gobo?
>
Having thought about it a bit more I came to the conclusion that one thing
I like about GoboLinux, is the long and hard-to-type names (and ofcourse
zsh's tab completion ;) ), so names like GoboInstall or GoboInstallTool is
prefered (actually I wont choose an abbreiation unless it's very, very,
very good).
Another "unofficial" name convention is to use simple words for
projects, like Compile, Manager, Freshen, Scripts, Bootstrap, etc
(which I think sound good combined with GoboLinux when describing them
unambiguously, such as "GoboLinux Compile", or even "Gobo Compile"). I
liked Jonatan's suggestion of "gobolinux tool box", so my derived
suggestion would be simply... Toolbox :) I think it sounds especially
appropriate because the toolbox "carries" the other tools :)
-- Hisham
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
