Date: Fri, 16 Jan 2004 15:03:06 +0200 (EET) From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: Ion-Mihai Tetcu <itetcu@apropo.ro> Cc: stable@freebsd.org Subject: Re: ports sup tag (was: Re: ) Message-ID: <20040116145335.G39895@atlantis.atlantis.dp.ua> In-Reply-To: <20040116140426.1706ca41@it.buh.cameradicommercio.ro> References: <20040116131248.G36380@atlantis.atlantis.dp.ua> <20040116140426.1706ca41@it.buh.cameradicommercio.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! On Fri, 16 Jan 2004, Ion-Mihai Tetcu wrote: > > > Users should not use tags for ports collection. It's > > > documentated also. > > > > Umm... What exactly is negative impact of using, for example, > > tag=RELEASE_5_2_0 for getting ports collection which came with 5.2-RELEASE > > via CVSup? > > None. But if you want the snap-shot of 5.2R's ports why cvsup ? The > cvsup will get you nothing. Then please tell me how can I get ports tree at the moment of tagging? Pre-release code freeze for 5.2 has been done in December, while 5.2-RELEASE has been available since only 12th of January. Where can I get this ports collection in the interim? As you know, distfiles for some ports have a bad habit of disappearing from the Net, so this delay is essential for me. BTW, if small but critical errors (such as different typos which happen time to time) found in ports tree between the tagging and release announcement, I'm sure that they will be corrected in RELEASE_x_y_z also, won't them? Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040116145335.G39895>