Date: Mon, 6 Nov 2006 22:49:05 -0600 From: "Jeff Hinrichs - DM&T" <jeffh@dundeemt.com> To: "Joerg Pernfuss" <elessar@bsdforen.de> Cc: cpghost <cpghost@cordula.ws>, Michael S <msherman77@yahoo.com>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: php5 issue Message-ID: <5aaed53f0611062049y14bb11e6kc74eac4b6799c82d@mail.gmail.com> In-Reply-To: <20061106204331.1c4affd4@loki.starkstrom.lan> References: <20061106183503.75661.qmail@web88312.mail.re4.yahoo.com> <454F8609.5060507@cordula.ws> <20061106204331.1c4affd4@loki.starkstrom.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I find it kind of weird that people click right through > `make config' without reading it. > Actually, the apache module was the default until recently. I normally set any non-defaut options in pkgtools.conf and keep things upgraded with portinstall/upgrade. The change caught me as well. (BATCH=YES) Granted the fix was in 20060506 UPDATING, which should be the first place to go if something goes amiss during an upgrade. However, there have been a number of changes to the php family of ports that impacted people who already had the port installed. I only wish that when these types of changes are made to a popular port that the maintainer would explain the reason for the pain -- due to the quality of the work done by the port maintainers (excellent, in my opinion) I assume it was for a good reason -- I just wish I was smart enough to figure out why or that they would note it, so I could read it and be smarter for it. <g> -Jeff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5aaed53f0611062049y14bb11e6kc74eac4b6799c82d>