Date: Mon, 19 Sep 2005 00:06:10 +0300 From: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> To: Kris Kennaway <kris@obsecurity.org> Cc: Clement Laforet <clement@FreeBSD.org>, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/devel/portmk/Mk bsd.apache.mk bsd.database.mk bsd.java.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.tcl.mk ports/devel/portmk/scripts distfiles.sh options.pl options.sh ranksites-fping.pl ... Message-ID: <20050919000610.381d93db@it.buh.tecnik93.com> In-Reply-To: <20050918205816.GA17932@xor.obsecurity.org> References: <200509182034.j8IKYCUv065506@repoman.freebsd.org> <20050918234714.41544927@it.buh.tecnik93.com> <20050918205816.GA17932@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 Sep 2005 16:58:16 -0400 Kris Kennaway <kris@obsecurity.org> wrote: > On Sun, Sep 18, 2005 at 11:47:14PM +0300, Ion-Mihai Tetcu wrote: > > On Sun, 18 Sep 2005 20:34:12 +0000 (UTC) > > Clement Laforet <clement@FreeBSD.org> wrote: > > > > > clement 2005-09-18 20:34:12 UTC > > > > > > FreeBSD ports repository > > > > > > Modified files: > > > devel/portmk/Mk bsd.port.mk bsd.port.subdir.mk > > > Added files: > > > devel/portmk/Mk bsd.apache.mk bsd.database.mk > > > bsd.java.mk bsd.tcl.mk > > > Removed files: > > > devel/portmk/Mk bsd.port.post.mk bsd.port.pre.mk > > > devel/portmk/scripts distfiles.sh options.pl options.sh > > > ranksites-fping.pl ranksites-geoip.pl > > > Log: > > > - Sync portmk with next exp-build patchset. > > > > Many thanks. Can we assume that from now on we'll have in this port > > the next set of changes one-two weeks before they'll be in the > > base ? > > This time it will be at least 1-2 weeks because we can't actually > commit the changes until 6.0 is out, but I don't know if we'll be able > to do this in future, because this would actually introduce delays > into the schedule, which really isn't something we need. > > Typically when one of us has time to run a test build, the changes are > selected then and put into testing almost immediately, with the > results known within a day or two. Waiting before starting the test > would run the risk of losing the window of availability to run the > test build, and waiting afterwards would allow new errors to creep in. What I would like is to have access to the "next set of changes" so that I can catch any problems I might have with my scripts that sometimes make use of "unsupported" features of *.mk Even 2-3 days would help. > > > - Remove temporarily all eik's work. We'll try to find a decent > > > way to deal with major changes. Of course we'll reuse his good > > > ideas > > > > The ranksites* part would be very useful. > > If you'd like to work on separating out those changes into a discrete > patch that can be tested, that would be great. It's for a long time on my to-do list (but what I have now won't do) and there are also others interested so who knows, maybe something good would come out eventually. :) -- IOnut Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050919000610.381d93db>