Date: Mon, 7 May 2007 18:21:46 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Brooks Davis <brooks@freebsd.org>, ports@freebsd.org Subject: Re: HEADS UP: xorg upgrade plans Message-ID: <20070507222146.GA57768@xor.obsecurity.org> In-Reply-To: <20070507220659.GC78665@graf.pompo.net> References: <20070502193159.GB42482@xor.obsecurity.org> <463F7236.4080108@FreeBSD.org> <20070507184231.GA50639@xor.obsecurity.org> <op.try3lgvv9aq2h7@mezz.mezzweb.com> <20070507201448.GA52651@xor.obsecurity.org> <op.try4tyhd9aq2h7@mezz.mezzweb.com> <20070507204414.GA53358@xor.obsecurity.org> <20070507205850.GA34916@lor.one-eyed-alien.net> <20070507220659.GC78665@graf.pompo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 08, 2007 at 12:06:59AM +0200, Thierry Thomas wrote: > Le Lun 7 mai 07 ? 22:58:50 +0200, Brooks Davis <brooks@freebsd.org> > ?crivait?: >=20 > > The other problem is that if you're going to automatically update all > > the dependencies for a port, you need to upgrade all the stuff that > > depends on them as well. For example the gettext upgrade got triggered > > on my laptop by upgrading something the used gmake. The result was that > > virtually nothing outside the base worked any more. Saving the shared > > library would have prevented this and allowed a more graceful upgrade > > over a few weeks. The fact that a basic desktop setup takes days to > > build on fairly fast hardware seems to be an indication that we need a > > workaround here. There are other possible solutions, but saving copied > > of libraries seems to be the accepted one at the moment. >=20 > For this kind of upgrades, it's possible to add >=20 > libgettextpo.so.1 libgettextpo.so.3 > libintl.so.6 libintl.so.8 >=20 > in your /etc/libmap.conf. Just delete these lines after the storm... It is possible, but this is not something that non-technical users will think of (nor should they have to). The question is whether portmaster is to be considered as a tool for advanced users only (those who are capable of cleaning up and repairing damage themselves when an upgrade fails), or if it is intended as a tool for ordinary users who don't want to (or are not capable of) doing this kind of manual repair work. If the goal is the former, then that's OK, but if it is the latter, then an honest evaluation leads one to conclude that portmaster is still in the process of maturing towards achieving this goal. Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGP6Z6Wry0BWjoQKURAmidAKDd/cYkNp0uD0FJEHbuDTNbLfXCYwCePq0/ iXrgjyt1h4lX11eZPqXbDEQ= =2NHE -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070507222146.GA57768>