Subject: Re: misc/8397: anoncvs needs a module entry for pkgsrc
To: Bjoern Labitzke <firstname.lastname@example.org>
From: Eric Mumpower <email@example.com>
Date: 09/13/1999 21:50:22
> If I understand you correctly, you want to be able to do
> a cvs checkout pkgsrc, right? At this moment I am doing an
> update of the pkgsrc-tree via AnonCVS and have been doing that
> for nearly two weeks now. Please try again...
No. I wish it to be *obvious* to the casual user who knows enough about CVS
to explore the repository before checkout using "cvs checkout -c" that the
pkgsrc module is in the pkgsrc directory. (Really, while this is a wise
first guess, it's not the only reasonable possibility.) In my case, I simply
guessed, and was pleased to discover that I had guessed correctly.
To be clear: I am not hzaving problems with CVS. I am suggesting a bit of
self-documentation in the form of a dummy module entry in the
I apologize, I assumed my intent would be clear without further explanation.
There are already redundant dummy modules defined for gnusrc, othersrc,
sharesrc, and syssrc. (They are not referred to by any other module; the
only purpose for these modules that I can imagine is to make clear the
modulenames which should be used for particular purposes.) I merely proposed
creating yet another dummy module for pkgsrc.