Gilles Detillieux wrote: > The drawback to using CVS is that everyone has to use it. You can't > really have an alternate method of updating the files, otherwise the > repository doesn't get updated.
Everyone already uses it. It's the best way to create a mirror for the maindocs. Mostly, if not all, mirrors are ran on 24/7 machines with a big internet pipe, and are managed on a routinely basis by profesionals, and they know CVS for sure and are using it. I don't think that there are 'personal' mirrors. Better still, is to use one program only for updating mirrors. That's why it would be nice if the patch site ran CVS (but it only has advantage if the 'files' can be mirrored with CVS). > Another option open to htdig developers is ssh access and the scp command. > Personally I like being able to use scp to copy in any contributed works. > I find this more convenient than the old method of using CVS. Is there > some way of setting up automatic updating/mirroring using ssh access? SSH/SCP can be used to copy, but I don't know if it can be used to update. I've used rsync over SSH for updating directories, and that works very well, so you'll need a third program to generate a list of files to be tranferred for updating the mirror. > Given the quirks with CVS on SF, I'd be a bit leary about using it, even > for a trial period, because it's sort of an all or nothing proposition. > Mind you, the maindocs updates have been going pretty well now, haven't > they? Ahhh, mirorring maindocs can go haywire if 'files' are added to the repository. Hmm, if that's so, let's not do it. --Jesse op den Brouw _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
