From owner-cvs-all Thu Feb 1 20:16:39 2001 Delivered-To: cvs-all@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 6E0E237B503; Thu, 1 Feb 2001 20:16:14 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f124GD935893; Thu, 1 Feb 2001 21:16:14 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102020416.f124GD935893@harmony.village.org> To: John Baldwin Subject: Re: cvs commit: src/release/picobsd/dial PICOBSD src/release/pic Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, Luigi Rizzo In-reply-to: Your message of "Thu, 01 Feb 2001 18:22:58 PST." References: Date: Thu, 01 Feb 2001 21:16:13 -0700 From: Warner Losh Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message John Baldwin writes: : Any repocopy does this. :) Moving sysintall put an 8 MB load on all the cvsup : servers, but I didn't get any big cries of objection to that. Didn't realize that.... : > The src/sys tree is slowly migrating. In the end it will likely be a : > large amount spent on copies there than moving release/picobsd would : > generate. : : Don't quite parse this, are you saying that src/sys changes will eventually : cost more in forms of repo-bloat than the picobsd move? If so, then I agree. Yes. : Of course, I have a somewhat cock-eyed view of what I would like src/sys to : look like: http://people.FreeBSD.org/~jhb/sysorg.txt. I've seen that and I'm not sure I like it.... : I just like cleaning up the tree in places. Ideally, IMO, : src/release should be a place to stick stuff used for building : releases, not a dumping ground. This is one of the reasons (among : others) that I moved sysinstall to src/usr.sbin/, as it is not a : release-only tool. Others have pointed out that picoBSD is just : another form of distributing code like the normal releases. I : personally feel that they are apples and oranges, but not everyone : will agree. But when you build a picobsd image, you are building a release. That's why it was originally placed in there. The original discussion said it was the least bad place for it in the tree. What if we have a TinyBSD that is a different animal than PicoBSD. Do we have a src/tinybsd and a src/picobsd as well? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message