On Fri, Sep 19, 2008 at 6:00 PM, Michael Homer <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 19, 2008 at 8:53 AM, Hisham <[EMAIL PROTECTED]> wrote:
>> 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 i
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
On Fri, Sep 19, 2008 at 2:03 PM, John Robert Beshir
<[EMAIL PROTECTED]> wrote:
> Hisham wrote:
>> On Wed, Sep 17, 2008 at 9:01 PM, Michael Homer <[EMAIL PROTECTED]> wrote:
>>> Hi all,
>>> I committed a modification to UseFlags yesterday/this morning to
>>> enable same-named flags for every installe
Hisham wrote:
> On Wed, Sep 17, 2008 at 9:01 PM, Michael Homer <[EMAIL PROTECTED]> wrote:
>> Hi all,
>> I committed a modification to UseFlags yesterday/this morning to
>> enable same-named flags for every installed program by default. The
>> program names are normalised to valid flag form (lowerca
On Wed, Sep 17, 2008 at 9:34 PM, Michael Homer <[EMAIL PROTECTED]> wrote:
> Me again,
> A couple of days ago I committed two new tools that Jonas and I had
> kicked around on #gobolinux on and off for while now:
> VersionExecutables and UnversionExecutables. VersionExecutables
> creates hard links
On Wed, Sep 17, 2008 at 9:01 PM, Michael Homer <[EMAIL PROTECTED]> wrote:
> Hi all,
> I committed a modification to UseFlags yesterday/this morning to
> enable same-named flags for every installed program by default. The
> program names are normalised to valid flag form (lowercase
> alphanumeric pl
