From owner-freebsd-doc Mon May 8 6:18:35 2000 Delivered-To: freebsd-doc@freebsd.org Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by hub.freebsd.org (Postfix) with ESMTP id 647C237B8DD for ; Mon, 8 May 2000 06:18:31 -0700 (PDT) (envelope-from bartequi@neomedia.it) Received: from bartequi.ottodomain.org (ppp1-pa5.neomedia.it [195.103.207.113]) by aragorn.neomedia.it (8.9.3/8.9.3) with SMTP id PAA20556 for ; Mon, 8 May 2000 15:18:28 +0200 (CEST) From: Salvo Bartolotta Date: Mon, 08 May 2000 14:20:24 GMT Message-ID: <20000508.14202400@bartequi.ottodomain.org> Subject: suggestion for the handbook: cvsup fine point ? To: freebsd-doc@FreeBSD.ORG X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear FreeBSD doc'ers, I was wondering whether the following suggestion was worth including in the handbook (and/or somewhere else). A few questions in ...-questions seem to indicate that a good number of people are missing this "fine point" -- albeit it IS described in the cvsup man pages, maybe in a somehow "embedded" form. Some information (and examples) on this issue can be found in the FAQs at http://www.polstra.com , ie on the site of the author of cvsup. Why not add e.g. to the chapter section on cvsup several examples concerning the list=3Dcvs: trick ? It might help people (to) correctly tag their cvsup files when updating their sources for the **first** time, or when **switching** from one Release to another -- e.g. when updating the 4-0 sources to -CURRENT for the first time. Thus, the checkouts file would be correctly created (or adopted if existing) by cvsup, its information being useful for this first update; also, NO file deletions would be omitted, and source trees would be correctly managed in this delicate transition. --------------------------- EXAMPLE I ------------------------------- file "standard-supfile_first-time" (to be used only for the **first** update from 4.0-R to -CURRENT): [...] src-all tag=3DRELENG_4_0_0_RELEASE list=3Dcvs:. (and the period after "cvs:" is essential.) REMARK The first update operation will not update anything per se; rather, it will generate the correct checkouts file. --------------------------- EXAMPLE II ------------------------------ file 4.x-stable-supfile_first-time (to be used only for the **first** update from 4.0-R to 4.0-S): [...] src-all tag=3DRELENG_4_0_0_RELEASE list=3Dcvs:RELENG_4 REMARK The first "update" operation will NOT change your sources; it will only generate the correct checkouts file. =A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7= =A7=A7=A7 GENERAL CASE =A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7= =A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7 First-time update supfile: [...] src-all tag=3DTAG_OF_WHAT_I_HAVE list=3Dcvs:TAG_OF_WHAT_I_WANT cvs-crypto tag=3DTAG_OF_WHAT_I_HAVE list=3Dcvs:TAG_OF_WHAT_I_WANT -------------------------- EXAMPLE III ------------------------------ First time update when going from 4-S to -CURRENT: TAG_OF_WHAT_I_HAVE=3DRELENG_4, TAG_OF_WHAT_I_WANT=3D. (and the period i= s essential.) REMARK Probably, in *such* cases (transition from a given -STABLE to -CURRENT), simply renaming the (existing) checkouts file does the job. I haven't actually tried this myself, though; I might just be missing another fine point in the fine point ... I hope that this information will somehow help, and that I have missed NO fine point(s) myself (!!) :-) Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message