cvsup-mirror rewrite

[Jeremie Le Hen]

[ This is a small conversation I had with jdp@ yesterday evening.  Hub
  owners, please, read it and let me know your feelings about this. ]

On Tue, Dec 07, 2004 at 07:38:27PM -0800, John Polstra wrote:
> On 07-Dec-2004 Jeremie Le Hen wrote:
> > I'm planning to rewrite some parts of cvsup-mirror to make it cleaner.
> > Here is what I want to do for the moment:
> > 
> >     o I wish to make the dependency on cvsupd optionnal for those like
> >       me who just want to have a local copy of the FreeBSD CVS
> >       repository.
> >     
> >     o I would also like to move etc/cvsup/update.sh to something like
> >       /usr/local/libexec/cvsup-mirror.sh, following the example of the
> >       atrun command executed from cron(8) [1].
> >     
> >     o I think it would be relevant to move the etc/rc.d/sup.client/
> >       directory to /var/db/, just as it has been done recently in
> >       RELENG_5 and HEAD for example supfiles [2].
> > 
> >     o Move cvsup-mirror specific files to etc/rc.d/cvsup/mirror/ to
> >       have a clearer hierarchy.
> > 
> > That's all what I thought about for the moment, but I'll maybe find
> > other things to do while working on it.
> > 
> > I prefer to taste your opinion on the subject before beginning my work.
> > Would you be interested in commiting such changes ?  Do you have any
> > comments on things I described above or additional ideas ?
> > 
> > [1] obiwan:libexec# grep atrun /etc/crontab
> >     */5     *       *       *       *       root    /usr/libexec/atrun
> > 
> > [2] obiwan:cvsup# grep /var/db /usr/share/examples/cvsup/standard-supfile
> >     *default base=/var/db
> 
> I think your ideas are reasonable, but they could cause problems for
> mirror sites that upgraded to a new version of cvsup-mirror.  Lots of
> files wouldn't be in the expected places.  On the other hand, it's not
> particularly easy to upgrade an existing cvsup-mirror installation
> even now.
> 
> If you want to make these changes, I think you should get the opinions
> of the folks on the freebsd-hubs mailing list first.  They're the main
> users of this port.
> 
> I don't have time to commit your changes, but I wouldn't object at all
> if you would (a) take over maintainership of the port, and (b) find
> another committer to do the commits for you.

In particular, I want to know if some hub administrators are against
this kind of changes and why.  Furthermore, I would like to gather
ideas on the hypotetical upgrade method.

Regards,
-- 
Jeremie Le Hen
jeremie at le-hen.org