[pkg-horde] tla primer slightly revised, Gregory's howto

[Lionel Elie Mamane]

On Tue, Jul 11, 2006 at 02:16:16AM +0200, Gregory Colpart wrote:

> On Mon, Jul 10, 2006 at 12:28:38PM +0200, Lionel Elie Mamane wrote:

> I have questions for next part :

>> Let's note that tla-load-dirs 1.0.29 contains support for "import"
>> instead of "commit", so that the procedure with tla_load_dirs for
>> "First commit of upstream sources" becomes:

> [...]
>>  # the following requires version 1.0.29 or later.
>>  $ tla_load_dirs "-sImport from HORDE_APPLI VERSION_NUMBER"

> Typo ? -> s#"-s#-s"#
> And why don't you precise path to load ?

Forgot it. Add it.

>>  # BEGIN: with version before 1.0.29
>>  # tla_load_dirs -n "-sImport from HORDE_APPLI VERSION_NUMBER"

> Same question : why don't you precise path to load ?

Same answer.

>>  $ YOUR-EDITOR `tla make-log`
>>  Enter text to comment your operation, for example "Import from HORDE_APPLI VERSION_NUMBER"

> not redondant with -s"log" ?

Yes, it is redundant. Sorry.

>>  $ tla import
>>  # END: with version before 1.0.29

> With tla_load_dirs 1.0.28, I use simply, e.g. :

> $ tla_load_dirs -v --summary='Import horde-sam 0.1-1' ../../horde-sam-0.1/

With tla_load_dirs 1.0.28, this will not work for the very initial
import (when it should do "tla import" at the end and not "tla
commit"), but will work for the new upstream versions past the first.

> I don't understand the subtil difference between 1.0.29 and
> < 1.0.29 versions

Versions < 1.0.29 have a bug where they will do "tla commit" instead
of "tla import" when this is necessary, that is in the very initial
first import. One has thus to add the "-n" option to keep it from
doing "tla commit" and issue "tla import" by hand. Version 1.0.29 will
automatically issue "tla import" when necessary, and "tla commit" when
necessary.

-- 
Lionel