Date: Mon, 09 Nov 1998 15:50:48 -0800 From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> To: asami@FreeBSD.ORG (Satoshi Asami) Cc: jkh@time.cdrom.com, mike@smith.net.au, mark@grondar.za, sos@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? Message-ID: <4353.910655448@zippy.cdrom.com> In-Reply-To: Your message of "Fri, 06 Nov 1998 14:57:48 PST." <199811062257.OAA10011@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> As for the package building itself, I think you got the wrong > impression. It was the idea from the very beginning that Justin was > going to build 3.0 packages. He's been the one that's been building > packages-current throughout its lifetime. (In fact, I have never > built packages-current since it split from packages-stable.) Ah. Sorry for the confusion over this then. I think Mike's just about got the new drive array ready (we got one of wcarchive's old cast-off drive racks) and we should be seeing at least 16-20GB of storage coming on line on bento very shortly. > (a) is not going to work. The ports collection is just not uniform > enough (like src) that it requires a lot of hand-tweaking to build. > > The problem is that for most committers, the ports collection is his > ports and some other ports it depends on. When you try to build the > entire thing, all hell breaks loose. See all the MANUAL_PACKAGE_BUILD > and LOOP_OPTIONs stuff? That's your chewing gum and duct tape right > there. Hmmmm. Well, while I can certainly understand the situation, I still worry somewhat about how well all of this is going to scale when we get up past 3000 packages. Sure, it's a very non-linear task and requires a large amount of special-case work, but then so does the building of any arbitrary port and it seems to me that there might (and I emphasize *might*) be just another layer of automation and abstraction we need to and can add here. If disk space is the prime motivator here then by all means let's add more disk. We have plenty of physical space in bento now that we've rack-mounted it and, as I noted, we now have a seperate drive array rack that can hold up to 9 drives. > Also, you can't just take a "snapshot" and call it a release. Unless > that automated builds sets FOR_CDROM, you'll have various bits that > can't be put on a CDROM on the ftp site. There is also an issue of Does this statement still hold in light of your recent commits to support cleaning of the package collection for this? > Besides, nobody around here has enough disk space to build the entire > package tree from the top. I don't even know how much space it takes > now, but my guess is about 15GB. (Subdirectories like lang and Hah. We can easily get twice that much space together without even breaking a sweat. Watch this space for details. ;) > Justin's help), minus the pay. If you give me a couple weeks' advance > notice, I can build the entire package tree for any CDROM easily. (I > do it every couple of weeks anyway---it's just a matter of doing it at > the right time.) OK. Well, then please consider November 15th your advance notice for a 2.2.8 release on November 30th. > As I see, the problem has always been the lack of communication > between you and me. There were a couple of times that I had a wrong > idea about the release date (once when I sent you a mail asking me and If this has been a problem then I apologise - I'll try to make a more concerted effort to keep you and the rest of the ports team in the communications loop. > Maybe we can set up a "release-engineers" alias or something that we > (you, I, msmith, and whoever else that's involved in that particular > release) use to communicate? Done: releng: jkh,asami,msmith,jseger,steve If you want anyone else added to the "releng" alias, please let me know. release-engineers is another alias for this alias, for the more literal-minded among us. :-) > Here's an idea. The only way automation will work is if you start > building every package with an empty /usr/local. If you can get me > enough diskspace, I'll promise to work on a scheme in which for each > port, a script will set up a chroot directory and build the package in > there. Actually we probably need multiple machines too, since it will > take a very long time (all dependencies will always be built from > scratch too) to do it this way. All of that is doable. I can't give you an 8 machine cluster, but I probably could arrange a 3 machine cluster (paddock, builder, bento) with a shared 30-40GB chunk of space and their own 9GB local caches for speed (build to cache, ship from cache to shared collection in the background). I'll take you up on that promise! :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4353.910655448>