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'm also not sure about the behavior of hardlinks when you > pack a tarball for a binary package (I'm guessing they duplicate by > default, keep that in mind). They do, but you can use the --exclude-from option to leave anything listed in R/VE out of the tarball. I'll add that to CreatePackage. SymlinkProgram can recreate the links on install.
Anybody who would find this particularly useful or particularly abhorrent should chime in. -Michael _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
