Re: [ITP] gt5-1.3 -- A terminal program to show disk usage and navigate between directories

[Jari Aalto <jari dot aalto at cante dot net>]

Peter Ekberg <peda-SamgB31n2u5IcsJQ0EH25Q@public.gmane.org> writes:

> On Wed, Feb 22, 2006 at 12:48:28AM +0200, Jari Aalto wrote:
>
>> "Dr. Volker Zell" writes:
>> 
>> >>>>>> Jari Aalto writes:
>> 
>> > Jari it would be nice if the two steps (pkg/spkg) in your build
>> > scripts behave like in other build scripts (g-b-s/Yaakov's
>> > Gentoo-based package build script). They should produce binary and
>> > source packages in the same directory in which the build script
>> > itself is located.
>> 
>> I saw two problems with it:
>
> *snip*
>
>>     2) Parallel development of many packages is possible only if
>>     all development is done within the "branch"
>> 
>>         ROOT
>>             package-a
>>                     version-1.1/
>>                     version-2.1/
>>                     version-3.1/
>>             package-b
>>                     version-1.1/-!-
>>                     version-2.1/
>>                     version-3.1/
>> 
>>     Suppose you're building in -!-, and the result [source].tar.gz and
>>     [bin].tar.gz are put ../ above. The you move to version-2.1/ and
>>     the results are again put ../ above.
>
> But will not the results be versioned?
> (But this does not refute your other arguments, of course)
>
> I.e:
> package-b-1.1-1-src.tar.bz2
> package-b-1.1-1.tar.bz2
> package-b-2.1-1-src.tar.bz2
> package-b-2.1-1.tar.bz2

Correct. But the idea is to keep the results within the branch. I
frequently move whole trees around like this:

    ROOT
        try
            package-a/
                    version-1.1/        .. Whoa doesn't build
                                        <time passes>
                    version-3.4/-!-     Success

        ok
            package-b/
                    version-1.1/    
                    version-2.1/    

            package-c/
                    version-1.1/
                    version-2.1/
        nok
            package-d/
                    version-1.1/
            package-e/
                    version-1.1/

Finally Cygwin compatible version had arrived (-!-) and the devel dir can
be merged with others:

    $ cd ../..      ( that is: ROOT/try )
    $ mkdir /ROOT/nok/package-a /ROOT/ok/package-a
    $ cp -r package-a/version-1.1 /ROOT/nok/package-a/
    $ cp -r package-a/version-3.4 /ROOT/ok/package-a/

Resulting structure:

    ROOT
        try
        ok
            package-a/
                    version-3.4/-!-     Success
            package-b/
                    version-1.1/    
                    version-2.1/    

            package-c/
                    version-1.1/
                    version-2.1/
        nok
            package-a/
                    version-1.1/        .. Whoa doesn't build
            package-d/
                    version-1.1/
            package-e/
                    version-1.1/


Jari