From owner-freebsd-hackers Fri Mar 26 10: 6: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 014201559A for ; Fri, 26 Mar 1999 10:06:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA09547; Fri, 26 Mar 1999 10:02:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Daniel Lang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make release - a nightmare In-reply-to: Your message of "Fri, 26 Mar 1999 13:40:15 +0100." <19990326134015.C26520@informatik.tu-muenchen.de> Date: Fri, 26 Mar 1999 10:02:55 -0800 Message-ID: <9545.922471375@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > this is a long story, I'm afraid, but I think > I identified some of the main problems, so maybe > they can be fixed.. Well, I think these basically miss one fundamental point: The release target isn't aimed at users. :) If you're going to roll releases, there are quite a few prerequisites to keep in mind. First off is the fact that this whole thing has been rolled for and by the release engineer(s) - it's not designed to be easy to use, simply to be comprehensive enough to build a complete release. This is why, for example, the encryption bits are non-optional. I expect to build both crypto and non-crypto bits since that's what a release contains. In any case, I'm sure the stuff could be cleaned up and I'm always willing to look at diffs, but just to make the point that this was never really meant to be all that clean in the first place - it's like the underneath of an escallator; only the service techs are really meant to be looking at it anyway. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message