RE: Loginfo for ampersand modules

[Jens Vonderheide]

> From: Larry Jones [mailto:address@hidden

> > When I just put the name of the "super module" into the loginfo file, no
> > update is done on commit. When I use DEFAULT or ALL, the checked-out
copy is
> > updated, but it is updated once for each module involved in the commit.
This
> > leads to conflicts in the checked-out copy.
>
> The first field in the loginfo file is a *directory* name, not a module
> name.  I don't understand why multiple updates would lead to conflicts
> -- if nothing's changed since the last update, it shouldn't do anything
> at all.

It seems that the update processes for each module are started concurrently
and somehow conflicting with each other.

Here are some examples:

The start:
handling module: kion
updating kion->HEAD on address@hidden:/home/kion via ext(ssh) from
localhost:/var/cvs/kion
handling module: kion
updating kion->HEAD on address@hidden:/home/kion via ext(ssh) from
localhost:/var/cvs/kion
handling module: kion
updating kion->HEAD on address@hidden:/home/kion via ext(ssh) from
localhost:/var/cvs/kion

Some indication that the processes are conflicting:
RCS file:
/var/cvs/kion/templates/_default/_default/childEmployee.calendar.js.inc,v
retrieving revision 1.1
retrieving revision 1.2
Merging differences between 1.1 and 1.2 into childEmployee.calendar.js.inc
kion/templates/_default/_default/childEmployee.calendar.js.inc already
contains the differences between 1.1 and 1.2
RCS file:
/var/cvs/kion/templates/_default/_default/employeeDataForm.einrichtung.tmpl,
v
retrieving revision 1.11
retrieving revision 1.12

And some real problems:
cvs update: move away
kion/templates/_default/_default/output.child.pdf.labels.inc; it is in the
way
C kion/templates/_default/_default/output.child.pdf.labels.inc
(The file in question was just added prior to the commit)


Hm, now that I read the acu output, I am thinking that perhaps I should be
configuring acu seperately for each "real" module. I'll try that...

Jens