Date: Mon, 28 Jan 2002 20:20:53 +0100 (CET) From: BOUWSMA Beery <freebsd-user@netscum.dyndns.dk> To: freebsd-ports@freebsd.org Subject: Pain with cvs checkouts from CVS ports repository Message-ID: <200201281920.g0SJKrO03154@beerswilling.netscum.dyndns.dk>
next in thread | raw e-mail | index | archive | help
Moin, moin!
I've nabbed the CVS repository in preparation to set up a mirror site
and thought to myself, "Self, why not *use* this repository with `cvs'
in order to keep up-to-date without wasting bandwidth by downloading
the same stuff again, and without bothering to configure a cvsupd
swerver?" And so I did. Or I tried.
First of all, it seems the following line in the CVSR00T/modules,v file
(and CVSR00T/modules) causes me no end of pain no matter what I do:
24253 docbook-241 ports/textproc/docbook-241
24254 docbook-300 ports/textproc/docbook-300
24255 docbook-310 ports/textproc/docbook-310
-> 24256 docbook-410/ ports/textproc/docbook-410/
24257 docbook-tdg ports/textproc/docbook-tdg
24258 docbook-to-man ports/textproc/docbook-to-man
24259 docbook-xml ports/textproc/docbook-xml
If someone would be so kind as to do whatever is needed to purge the
offending trailing slash, I'd be overjoyed. Or explain why it's
there, or something. It sure makes `co docbook-410' difficult.
Secondly, I'm not sure if I'm supposed to be able to use `cvs co' on
the local CVS RCS file repository to get the needed ports one at a
time (or update them, as I see fit), or if there's a special way
that I should be doing this, for when I do the above, for many ports,
I get both the old-fashioned pkg and patches and files/md5 junk, plus
the present way to store all this, which triggers the following lines
in the bsd.port.mk file for most (but not all) ports:
.if (!defined(PATCHDIR) && exists(${MASTERDIR}/patches)) || \
(!defined(PKGDIR) && exists(${MASTERDIR}/pkg)) || \
(!defined(MD5_FILE) && exists(${MASTERDIR}/files/md5))
pre-everything::
@${ECHO} "Error: your port uses an old layout. Please update it to matc
h this bsd.port.mk. If you have updated your ports collection via cvsup and are
still getting this error, see Q12 and Q13 in the cvsup FAQ on http://www.polstr
a.com for further information."
Shouldn't the old-fashioned files be moved into an Attic directory or
otherwise cleared from view so I don't check them out, or is this not
a supported way for me to keep up-to-date, as it were?
(Yeah, I'm sure that if I were to `cvsup' from my CVS repository rather
than `cvs co', I wouldn't have this problem, but I'd like to hear that
`cvs co' isn't a supported way to do things before I give up and conform)
thnks,
barry bouwsma
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201281920.g0SJKrO03154>