[Ltib] -m release and CVS ltib module

[Andrea Galbusera]

Hi Stuart,
I'm still experimenting with the '-m release' option of ltib.

The problem I'm facing is in the 'CVS export' command that is embedded
in the release procedure. As you may remember from my previous threads
on the subject, I'm using a locally hosted CVS tree of ltib: the point
seems to be that this tree in not uniquely called 'ltib' but something
like 'myproject/mysubproject/ltib-something'. I suspect this is making
the following code in Ltibutils.pm to do something unexpected.

    if(-d "$cf->{top}/CVS") {
        system_nb("cvs export -kv -d $dir -r $tag ltib") == 0 or return;
    }

In fact, this is not failing with an error but simply no $dir is created
and nothing at all is exported. Following operations will than fail,
since 'stage' dir is missing.

I'd like to have your opinion on this... having a local CVS repository
for ltib is supported (as discussed in previous threads), so I should
not be too much out of path. To avoid changing anything in ltib, of
course, I could enforce 'ltib' to be the name of the module in the
repository or, at least, I could create an alias module (in the CVS
meaning of this term) to make 'ltib' point at the right location in the
repository. But what if more than one tree of ltib is present in the
repository (as, in fact, is on my repository)? Is there any chance to
instruct cvs to catch the module name from the sandbox it is run from?

Thanks for your always precious help!
Andrea