DragonFly users List (threaded) for 2008-01
DragonFly BSD
DragonFly users List (threaded) for 2008-01
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: cvsup

From: Vincent Stemen <vs1@xxxxxxx>
Date: 20 Jan 2008 02:17:31 GMT

On 2008-01-19, Simon 'corecode' Schubert <corecode@fs.ei.tum.de> wrote:
> This is a multi-part message in MIME format.
> --------------020108070307000905080907
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Content-Transfer-Encoding: quoted-printable
> Vincent Stemen wrote:
>> Also, if nobody has written one or is working on one, I am considering =
> writing
>> a script to provide basic cvsup like features/functionality for reposit=
> ory
>> updates via rsync.
> I'm not sure what you mean with that.  Isn't calling rsync enough?  Maybe=

It wasn't for me.  I had research who the rsync mirrors are, look up and
determine the appropriate command line switches, post on the mailing
list for help because I did not know the repository directory paths on
the rsync servers, was not yet familiar with the rsync commands to get
that information directly from the server (each one is different) and
the instructions were not documented on the DragonFly web site like they
are for cvsup, and write a custom shell script loop to run rsync to
update each directory (CVSROOT, doc, src, etc).

Contrast that with having pre-configured cvsup files that come with the
base system and just running "cvsup -f path/to/cvsup-file".

The updatecvs script you posted looks like it is heading in the
direction that I am talking about.  Although I was considering making it
for just rsync, since we already have cvsup, and setting up
a pre-configured configuration file[s] for each of the available rsync
servers.  It looks like your script is using config files.  I will study
it more closely to see how close it is to what I am thinking about


[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]