Date: Mon, 24 Apr 2006 21:29:39 +0930 From: Ian Moore <no-spam@swiftdsl.com.au> To: freebsd-questions@freebsd.org Subject: Re: A portupgrade question Message-ID: <200604242129.45420.no-spam@swiftdsl.com.au> In-Reply-To: <4166.194.201.68.18.1145879418.squirrel@www.firebadger.net> References: <200604242043.25020.no-spam@swiftdsl.com.au> <200604242046.42039.no-spam@swiftdsl.com.au> <4166.194.201.68.18.1145879418.squirrel@www.firebadger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Monday 24 April 2006 21:20, Richard Collyer wrote: > On Mon, April 24, 2006 12:16 pm, Ian Moore wrote: > >> Hi, I've got a question about portupgrade and something that's happened > >> with it a couple of times now. The last 2 times libgda has been > >> upgraded, > >> I've run portupgrade -a to upgrade a bunch of ports, including libgda. > >> > >> <snip> > > I always use portupgrade -aR to make sure dependencies are done. However > with mysql I find that portupgrade is not the best. > > Personally I would update ports tree (cvsup), cd to mysql ports directory, > make clean && make && make deinstall && make reinstall > > Never had a problem doing it that way. Yes, that would fix the problem, but I'm just curious about what causes the problem in the first place, given that portupgrade rarely seems to have these kind of problems. Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBETL2xPUlnmbKkJ6ARAmo+AJ9js5/lDOVahRf+0dvXdG2TAWO8zgCeNpeH GdL7fXASKdtrQp/EwLiNZ/E= =3oiy -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604242129.45420.no-spam>