Date: Sat, 31 Oct 1998 13:37:18 -0600 (CST) From: Steve Price <sprice@hiwaay.net> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Satoshi Asami <asami@FreeBSD.ORG>, mike@smith.net.au, mark@grondar.za, sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? Message-ID: <Pine.OSF.4.02.9810311311490.917-100000@fly.HiWAAY.net> In-Reply-To: <15699.909845800@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 31 Oct 1998, Jordan K. Hubbard wrote: # > very hard to detect on the building machine. The scheduling, which # > didn't leave him any time to put the ELF packages up for testing # > before the release, is at fault. # # You can say that again. Despite having plenty of warning, and we're # talking several month's worth here, the task was apparently dumped at # the very last moment on Justin and Steve. I know that Steve certainly # wasn't very happy about how this was done and it certainly took Mike # and I by surprise as well - there was some even doubt, for awhile # there, as to whether 3.0 would ship with a packages collection at all. Yes, I was indeed frazzled. Justin did a great job! I just wished he had let me help a wee bit more. I'm sure he got quite annoyed after awhile with all my "here's a patch" messages. It was just too much for one person to do in the limited time available. # In any case, all finger-pointing and indignation aside, if the # ports/packages phase of each new release is to occur both on-time and # with minimum stress on all concerned, we're going to have to figure # out well in advance just who's going to take on the job of physically # generating and segregating all the packages and distfiles. I # certainly don't want to be scratching my head and trying to figure out # who's "job" it's even supposed to be a day before a release is due and # the various ports volunteers don't want to be stuck with doing the job # on a moment's notice, either. I know my half-witted attempt at creating a tool to help with this flopped miserably, but my offer still stands. I'd like to talk to you some more about what you require in such a tool. # My suggestion would be that we either: a) go to some sort of # automation scheme which [re]builds packages on an ongoing basis and, # at release time, I just take a snapshot of the collection or b) We try I've got a reasonably fast, well-connected machine that I could offer up to help with this. All I need is a little direction from Justin on how he setup his chroot'd build environment. # appointing a ports/packages releasemeister who's responsible for doing # in ports what I do for src each time a release rolls around. This Having more than one would be even better. :) I'll volunteer to be one of 'em for the next release. # person could be paid since it's important to Walnut Creek CDROM # that packages and distfiles be rendered into ISO images periodically, # especially now that we have this "toolkit" CD for FreeBSD in addition # to the usual 4 CD sets. # # Thoughts? # # - Jordan # # To Unsubscribe: send mail to majordomo@FreeBSD.org # with "unsubscribe freebsd-current" in the body of the message # 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?Pine.OSF.4.02.9810311311490.917-100000>