Subject: Re: CVS commit: pkgsrc/devel/generate
To: D'Arcy J.M. Cain <>
From: grant beattie <>
List: tech-pkg
Date: 08/22/2004 19:14:09
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Aug 22, 2004 at 03:30:56AM -0400, D'Arcy J.M. Cain wrote:

> Sorry, cut and paste error.  The command I used was;
> cvs -q -d import pkgsrc/devel/generate TNF \
>    pkgsrc-basecvs


> I got it from that page in the first place.  I did work it out and, in
> fact, recall having to do the same thing last time I imported a package.
>  What I had to do after the import is remove the directory and then cvs
> update to restore it from the repository.  So, the import command
> imports it into the repository but does not set up the local copy.

right - that's how imports work. I normally import from a random local
directory and then "cvs update" in the target location to get my local
checked out copy.

> If this is correct I can update the document but it feels klugish to me.
>  Is this correct?  I guess the correct way is to import from outside the
> CVS repository but I tend to build these packages in the repository so
> that I can do complete testing.

that also works, and I've done that in the past, too.


Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.4 (NetBSD)