> > Hi,
> >
> > I though that once a group was added to the system group file (such as
> > /etc/group), the backend didn't try to install the
> > repository/webpages/download area.
> >
> > It appears that all groups are 'recreated' each time you use
> > sv_groups. I mean, the the system group file is left updated, but
> > CvsMakeArea and other backend procedures are called.
> >
> > Usually this doesn't matter because CvsMakeArea & co exit when they
> > see that the directory they plan to creat is already present. But this
> > is no good for the way we update webpages at Savannah (ie ask the
> > remote machine to update using a 'webservice' call).
> 
> Sure, the backend as not really been designed to be run as a frontend
> of something else. In other words, the backend should be theoretically
> run on the machine that serves the webpages. Whatever. 
> 
> I do not really understand the exact problem you have, can you provide
> more details?

The way we have to update the www.gnu.org and www.nongnu.org webpages
is to call a CGI script using curl that will trigger a checkout and
update/create the remote webpages. They will then be updated by a
cronjob at www.nongnu.org. So, if the CGI script is called during
creation *and* each time sv_groups is launched at Savannah, it is not
good for us. Above all, we do not know whether the webpages are
already created or not, so we cannot stop calling the CGI scripts
during later sv_groups executions.

But, what I am wondering is why calling CvsMakeArea & co at each
sv_groups call. I considered those are useful only at project
creation.


> > Is this normal? It could actually be a bug in a boolean expression in
> > "if ($no_etc && !$exists) { <do nothing> } else { <update system> }".
> 
> No, this test have a completely different purpose (see the comment
> that come along this test.

I understood the reason of the first test.

What I meant, is that maybe you intended to write something like:
if ($no_etc && !$exists) { <do nothing> }
elsif ($exists) { <do nothing> }
else { <update system> }

I still do some "boolean bugs" sometimes, so it could have been a bug
:)


> > Incidentally, this behavior also led my test install to reuse the
> > existing "gnats" group from Debian, while not creating the associated
> > "webgnats" one and ruining the 'gnats' project installation.
> 
> The current CVS no longer mess with existing groups.

I use the current CVS. Do you mean the current CERN branch?

-- 
Sylvain

_______________________________________________
Savane-dev mailing list
[EMAIL PROTECTED]
https://mail.gna.org/listinfo/savane-dev

Reply via email to