2008/9/19 Michael Homer <[EMAIL PROTECTED]>: > On Fri, Sep 19, 2008 at 8:53 AM, Hisham <[EMAIL PROTECTED]> wrote: >> On Wed, Sep 17, 2008 at 9:34 PM, Michael Homer <[EMAIL PROTECTED]> wrote: >>> VersionExecutables >>> creates hard links to the executables within a program, named with the >>> version of the program they belong to. >>> I would like to enable this by default, and possibly even make it >>> mandatory so that recipes can rely upon the behaviour. >> I think this would make /S/L/E too polluted. Perhaps enabling it for >> some packages (eg, in the Qt recipe) would be fine, but not for every >> package. > That's another option. For my use, there's really no cost to extra > entries, so the benefit of having access to every installed version > all the time outweighs it. Somebody who accesses /S/L/E directly a lot > might have a different experience. Enabling it by default for a > specific list of programs and optionally for the rest might be a good > way to get the best of both worlds, though I still lean towards always > and everywhere for consistency's sake.
I agree that the cost for versioned binaries are much less then the benefit that comes from it. What I do think may cause an issue is signing of programs/packages. As versioned binaries should be a user option packages should not contain them but they should be created by SymlinkProgram. This causes the FileHash to be out of sync, forcing the user to resign the program if he/she should be able to verify it later. Of course this is no problem if versioned binaries are adopted throughout. -- /Jonas _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
