Date: Wed, 26 May 2010 22:07:19 -0400 From: Wesley Shields <wxs@FreeBSD.org> To: "Philip M. Gollucci" <pgollucci@p6m7g8.com> Cc: cvs-ports@FreeBSD.org, "Philip M. Gollucci" <pgollucci@FreeBSD.org>, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/www/apache20 Makefile ports/www/apache20/files patch-pcre.diff Message-ID: <20100527020719.GC8384@atarininja.org> In-Reply-To: <4BFD9FC1.8070207@p6m7g8.com> References: <201005261930.o4QJUjIr095703@repoman.freebsd.org> <20100526221248.GA8384@atarininja.org> <4BFD9FC1.8070207@p6m7g8.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 26, 2010 at 10:25:05PM +0000, Philip M. Gollucci wrote: > On 05/26/10 22:12, Wesley Shields wrote: > > On Wed, May 26, 2010 at 07:30:45PM +0000, Philip M. Gollucci wrote: > >> - This includes an MMN bump which means you will need to recompile all your > >> modules. With ports this will happen when you upgrade via portmaster or > >> portupgrade. If you have any modules outside of ports they will need to > >> be recompiled too. > > > > I don't use Apache but it seems to me that if a recompile of all modules > > is required PORTREVISION should be bumped on all of them. > > > > -- WXS > > You know you are right. I'd like to let the dust settle a little bit 1st > though and make sure the current www/apache20 does what we all expect. I don't mean to be an arm-chair critic here but I do have the interests of ports users in mind when I say this... I haven't been following your changes but it seems to me that if there is a lot of churn it may be prudent to slow down and allow time for bugs to shake out before making more changes. If they all must be made at once for a technical reason then please ignore my previous statement. I really have very little clue on how all these Apache things work. :) > You don't technically need to recompile them. > 1) if they check the mmn and complain > 2) if the api change actually affects you. > fwiw, it doesn't affect php or mod_perl which are both pretty > massive. > > however, recompiling them is never a bad idea; but due to all the recent > changes in apache land, someone making it through here without > recompiling everything is unlikely. Understood. I'd just like to see the least painful update path possible for users. If modules must be recompiled we should bump them, regardless of the chances of someone not making it through without rebuilding on their own. I'm not requesting that this be done but it is something to consider once the dust settles a bit, like you said. -- WXS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100527020719.GC8384>