Date: Tue, 19 Jun 2007 18:00:15 +0200 From: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> To: tradigan@newrevolutions.net Cc: freebsd-questions@freebsd.org Subject: Re: Portsnap Message-ID: <4677FD8F.1020803@gmx.de> In-Reply-To: <50297.208.40.168.12.1182268291.squirrel@www.newrevolutions.net> References: <50297.208.40.168.12.1182268291.squirrel@www.newrevolutions.net>
next in thread | previous in thread | raw e-mail | index | archive | help
tradigan@newrevolutions.net wrote: > Hi all, > > I have just started using portsnap and I must say that I like it.. With > that said, I am noticing something here that maybe a configuration issue > on my end, but here is the deal: > > I have a newly installed 6.2 box, and I ran portsnap fetch followed by > portsnap extract.. This updated the ports tree just fine.. > > Now, I know that /usr/ports/sysutils/portupgrade was moved to > /usr/ports/ports-mgmt/portupgrade. This is visible when you use CVSup to > update the ports tree (ie: /usr/ports/sysutils/portupgrade does not > exist). However with portsnap, the /usr/ports/sysutils/portupgrade > directory still exists. Is there a way to get portsnap to remove ports > that were removed and/or moved? Actually it does that, but only if the files have been created by it. I think the manual states that you should 'rm -rf /usr/ports' before using portsnap for the first time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4677FD8F.1020803>