Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Mar 1998 10:40:31 -0700 (MST)
From:      Wes Peters - Softweyr LLC <softweyr@xmission.com>
To:        software@kew.com (Drew Derbyshire - UUPC/extended software support)
Cc:        stable@FreeBSD.ORG
Subject:   Re: after the release ...
Message-ID:  <199803201740.KAA03231@xmission.xmission.com>
In-Reply-To: <35127463.6ACB464@kew.com> from "Drew Derbyshire - UUPC/extended software support" at Mar 20, 98 08:51:31 am

next in thread | previous in thread | raw e-mail | index | archive | help
Eivind Eklund wrote:
% Good suggestion!  Go ahead and do it; I promise to post comments about
% your design when you post it, and I'm sure Jordan and Mike will, too.

Drew Derbyshire replied:
> Drop dead.  You can say it's boring to do and that Real Programmers (TM) don't
> need it, go ahead, but I don't need the sarcasm.
> 
> You can disagree with me, but I don't need to be ridiculed for making a valid
> suggestion.  

You misunderstood, he was neither disagreeing with you nor ridiculing
you.  He was simply inviting you to participate.  Believe me, I've seen
this before.

You have a great idea here, but the FreeBSD core team is already
involved in their pursuits.  If you want to do this, get together a
team to help you, come up with a design, float it around for comments,
then get busy coding.

> I neither a CVS expert

So you have some studying to do.

> nor directing FreeBSD release policy.  I'm only

You're being offered a position to direct a portion of it.  Since what
you propose won't change the source tree or the exiting release process
at all, the worst you can do is waste your time.  This isn't some giant
corporation with thousands of approvals to get.  Just do it!

> pointing out a failure in the FreeBSD release cycle, as Jordan pointed out HP
> and Sun have bugs, but THEY have a packaged patch process.  FreeBSD does not,
> it only has "upgrade to the next release" or hand patch any fixes into the
> source and rebuild.  Adding such a patch function seems to be an issue of
> packaging a limited number of critical changes (in 2.2.5 for example, it would
> have been the lpd and the security fixes) into a package.  Under System V, it
> would be pkgadd.  Under FreeBSD the best method seems to be ports.

I'd prefer to see binary packages myself; they're easier to install.

As I said, you have a good idea here.  Your help is needed to make it
happen.  This is as good a forum as any to gather help, advice,
criticism, flames, and anything else you may want or need.  This is a
"stable" issue, so this is an appropriate forum.

So?

-- 
          "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                       Softweyr LLC
http://www.xmission.com/~softweyr                       softweyr@xmission.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803201740.KAA03231>