Bug 29767

Summary: incorrect description of 'standart-supfile'
Product: Documentation Reporter: kunia <kunia>
Component: Books & ArticlesAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description kunia 2001-08-16 08:50:02 UTC
        standard-supfile in -stable now gets you the -stable sources, but it
        is pointed inside the file that it contains "CVSup collections" for
        current-sources.

How-To-Repeat: enigma# head -4 standard-supfile
# $FreeBSD: src/share/examples/cvsup/standard-supfile,v 1.17.2.2 2001/04/11 21:5
0:13 nik Exp $
#
# This file contains all of the "CVSup collections" that make up the
# FreeBSD-current source tree.
enigma# head -4 stable-supfile
# $FreeBSD: src/share/examples/cvsup/stable-supfile,v 1.19.2.4 2000/08/18 18:50:
21 jkh Exp $
#
# This file contains all of the "CVSup collections" that make up the
# FreeBSD-stable source tree.
enigma# grep -v # standard-supfile > 1
enigma# grep -v # stable-supfile > 2
enigma# diff -u 1 2
enigma#
Comment 1 ru freebsd_committer freebsd_triage 2001-08-16 08:58:13 UTC
On Thu, Aug 16, 2001 at 10:43:03AM +0300, Olexandr Kunytsa wrote:
> 
> standard-supfile in -stable now gets you the -stable sources, but it
> is pointed inside the file that it contains "CVSup collections" for
> current-sources.
> 
And also in README.  I think that either

	standard-supfile should be deleted from -STABLE

*OR*
	standard-supfile should be (repo)moved to current-supfile
	in -CURRENT, and MFC'ed to -STABLE.  With corrections to
	README.


Cheers,
-- 
Ruslan Ermilov		Oracle Developer/DBA,
ru@sunbay.com		Sunbay Software AG,
ru@FreeBSD.org		FreeBSD committer,
+380.652.512.251	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age
Comment 2 ru freebsd_committer freebsd_triage 2001-08-16 09:09:08 UTC
Responsible Changed
From-To: freebsd-doc->jdp

John, could you please look at this?
Comment 3 ru freebsd_committer freebsd_triage 2001-08-16 17:37:36 UTC
On Thu, Aug 16, 2001 at 07:59:07AM -0700, John Baldwin wrote:
> 
> On 16-Aug-01 Ruslan Ermilov wrote:
> > The following reply was made to PR docs/29767; it has been noted by GNATS.
> > 
> > From: Ruslan Ermilov <ru@FreeBSD.ORG>
> > To: Olexandr Kunytsa <kunia@x-telecom.net>
> > Cc: FreeBSD-gnats-submit@FreeBSD.ORG
> > Subject: Re: docs/29767: incorrect description of 'standart-supfile'
> > Date: Thu, 16 Aug 2001 10:58:13 +0300
> > 
> >  On Thu, Aug 16, 2001 at 10:43:03AM +0300, Olexandr Kunytsa wrote:
> >  > 
> >  > standard-supfile in -stable now gets you the -stable sources, but it
> >  > is pointed inside the file that it contains "CVSup collections" for
> >  > current-sources.
> >  > 
> >  And also in README.  I think that either
> >  
> >       standard-supfile should be deleted from -STABLE
> >  
> >  *OR*
> >       standard-supfile should be (repo)moved to current-supfile
> >       in -CURRENT, and MFC'ed to -STABLE.  With corrections to
> >       README.
> 
> Erm, in the original discussion about this, there was the point that
> 'standard-supfile' was supposed to follow whatever current branch you were on
> at the time.  Thus, on 4.x, standard-supfile follows RELENG_4, on 4.3, it
> follows RELENG_4_3, and on -current it follows HEAD.
> 
But it doesn't, in fact, follows 4.3 on RELENG_4_3, it's still set to
RELENG_4 there.  Nor it is to fetch RELENG_4_3 in RELENG_4_3_0_RELEASE.
And `standard' comes yet from `crypto' times, it assumes `non-standard'.

How about this?  For X.Y release, that would be:

release-supfile		RELENG_X_Y_RELEASE
bugfix-supfile		RELENG_X_Y
stable-supfile		RELENG_X
current-supfile		.

For -CURRENT, only stable-supfile and current-supfile make sense probably.


Cheers,
-- 
Ruslan Ermilov		Oracle Developer/DBA,
ru@sunbay.com		Sunbay Software AG,
ru@FreeBSD.org		FreeBSD committer,
+380.652.512.251	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age
Comment 4 John Baldwin freebsd_committer freebsd_triage 2001-08-16 21:39:28 UTC
On 16-Aug-01 Ruslan Ermilov wrote:
> On Thu, Aug 16, 2001 at 07:59:07AM -0700, John Baldwin wrote:
>> 
>> On 16-Aug-01 Ruslan Ermilov wrote:
>> > The following reply was made to PR docs/29767; it has been noted by GNATS.
>> > 
>> > From: Ruslan Ermilov <ru@FreeBSD.ORG>
>> > To: Olexandr Kunytsa <kunia@x-telecom.net>
>> > Cc: FreeBSD-gnats-submit@FreeBSD.ORG
>> > Subject: Re: docs/29767: incorrect description of 'standart-supfile'
>> > Date: Thu, 16 Aug 2001 10:58:13 +0300
>> > 
>> >  On Thu, Aug 16, 2001 at 10:43:03AM +0300, Olexandr Kunytsa wrote:
>> >  > 
>> >  > standard-supfile in -stable now gets you the -stable sources, but it
>> >  > is pointed inside the file that it contains "CVSup collections" for
>> >  > current-sources.
>> >  > 
>> >  And also in README.  I think that either
>> >  
>> >       standard-supfile should be deleted from -STABLE
>> >  
>> >  *OR*
>> >       standard-supfile should be (repo)moved to current-supfile
>> >       in -CURRENT, and MFC'ed to -STABLE.  With corrections to
>> >       README.
>> 
>> Erm, in the original discussion about this, there was the point that
>> 'standard-supfile' was supposed to follow whatever current branch you were
>> on
>> at the time.  Thus, on 4.x, standard-supfile follows RELENG_4, on 4.3, it
>> follows RELENG_4_3, and on -current it follows HEAD.
>> 
> But it doesn't, in fact, follows 4.3 on RELENG_4_3, it's still set to
> RELENG_4 there.  Nor it is to fetch RELENG_4_3 in RELENG_4_3_0_RELEASE.
> And `standard' comes yet from `crypto' times, it assumes `non-standard'.

Of course it doesn't, this was the _proposal_.  I think standard-supfile should
be fixed to do that personally.  Go look at the archives on -arch on this one
though, as there was some sort of decision made.  If you want to bring this all
up again, I suggest you do it on -arch.

> How about this?  For X.Y release, that would be:
> 
> release-supfile               RELENG_X_Y_RELEASE

No point, they already have this on their box or via hte CD's or what not, so
no need to cvsup.

> bugfix-supfile                RELENG_X_Y

It's not bugfixes, it's major security fixes only.

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
Comment 5 colin.percival 2003-02-12 04:17:12 UTC
   This PR can be closed -- it's obsolete, and jdp agrees that it can be 
closed (but hasn't gotten around to it yet).

Colin Percival
Comment 6 John Polstra freebsd_committer freebsd_triage 2003-05-26 19:38:46 UTC
Responsible Changed
From-To: jdp->freebsd-bugs

Give up responsibility for this PR.  I can't seem to get excited 
about it.
Comment 7 Ceri Davies freebsd_committer freebsd_triage 2003-11-07 20:51:40 UTC
State Changed
From-To: open->closed

This file is now correct on RELENG_4.