From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: Andrew Cagney Cc: overseers Subject: Re: CVSup update Date: Wed, 05 Apr 2000 08:04:00 -0000 Message-ID: <31181.954947027@upchuck> References: <38E99874.DA1A8AF3@cygnus.com> X-SW-Source: 2000-q2/msg00038.html Message-ID: <20000405080400.d1FnIMY1WcxXaaAi0fdqTESSN5x4hruMBDzeWpWVA7U@z> In message < 38E99874.DA1A8AF3@cygnus.com >you write: > FYI, > > I've got CVSupD running from my local directory/account (it is > configured to only accept connections from my machine :-). Well, I just had to change that :-) I added my box. > The next steps I can see are: > > > o an account - anoncvs was agreed Yup. > o a common config directory (and under CVS). > > see: > ~cagney/cvsup > for the basic contents. I've pump primed > it with a standard configuration for all existing > cvs repositories. eg: > ~cagney/cvsup/sup/src/src > ~cagney/cvsup/sup/src/releases > ``releases'' lists the sub releases > for ``src''. Currently each repository > has only a full release (``src'' here). > > I think this needs to be setup so that people > can maintain it using cvs (like CVSROOT) > with any edited files auto-installed into > the cvsup config tree. Sounds like the right way to go. Or if we find that they're all basically the same and static, then having them set up as SOP for new projects might be just as effective with less work. > o somewhere to put the log file How about /var/log/cvsupd.log? > o something to start cvsupd during boot. If we're happy with letting a few folks loose with this, then let's do it. How do you want the service started (ie, options and the like). > o me archive cvsupd in /usr/local/somewhere Yup. > One implementation note. I think I can pervert the cvsupd config so > that it looked for (using SRC as an example): We can tackle this separately from the basic service if you'd like. jeff