Date: Sat, 4 Apr 2009 19:02:46 -0500 (CDT) From: "Doug Poland" <doug@polands.org> To: "Matthew Seaman" <m.seaman@infracaninophile.co.uk> Cc: questions@freebsd.org Subject: Re: portupgrade fu... AKA there has to be a better way Message-ID: <75424c1e194a143415b99e169b0588a3.squirrel@email.polands.org> In-Reply-To: <49D7AFC9.9090708@infracaninophile.co.uk> References: <49D7AC35.7060000@polands.org> <49D7AFC9.9090708@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, April 4, 2009 14:06, Matthew Seaman wrote: > Doug Poland wrote: >> Hello, >> >> I'm upgrading a server from 6.4 to 7.1 and am going through the >> relative pain of re-compiling all the ports. It's not as easy >> "portupgrade -af" because of all the special handling instructions >> of many ports. >> >> I have not found an "easy" way to keep track of the ports that need >> to be forcibly updated but have not undergone a version change. >> Because I approach the upgrade in steps, I need to run portupgrade >> several times but want to exclude stuff already compiled under 7.x. >> >> What I need is a command like: >> >> # portupgrade -af -x "already compiled on 7" >> >> >> Suggestions, comments, rebukes welcome. > > Assuming you start the upgrade today, then: > > # portupgrade -af -x ">=2009-04-04" > hmmm, I don't think it gets much easier than that. Thanks! -- Regards, Doug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?75424c1e194a143415b99e169b0588a3.squirrel>