port config questions

Gerard Seibert gerard at seibercom.net
Mon Oct 17 14:35:24 PDT 2005


On Monday, October 17, 2005 5:13:28 PM, Chris <chris at childeric.freeserve.co.uk>
Subject: port config questions
Wrote these words of wisdom:

> Hi
> 
> Q1 To celebrate upgrading my desktop box to 6.0RC1 I am also upgrading 
> all my ports with portmanager. Before I ran portmanager I deleted all my 
> distfiles and ran portupgrade -arRfF to fetch a brand new set (I had far 
> too many stale ones). I notice that for example all the mplayer skins 
> distfiles have been downloaded despite /var/db/ports/mplayer/options 
> saying WITHOUT_SKIN_...=true for most of them. Is there some way to make 
> portupgrade respect config files in /var/db/ports/?
> 
> Q2 Can I tell portupgrade to go through the configs of all the ports it 
> is going to upgrade so that I can set them all in one go and then let 
> portupgrade (or portmanager) get on with things unattended? If not would 
> this be a useful addition to portupgrade functionality? I would like to 
> include options that are in Makefiles as well as 'make config' menus.
> 
> Thanks
> 
> btw thank you to the author of portmanager, it's wonderful (and I love 
> the way it works by making excuses not to do things. :-D)
> 
> Chris

***** REPLY SEPARATOR *****
On 10/11/2005 5:29:42 PM, Gerard Replied:

Portmanager has a configuration file located at:

/usr/local/etc/portmanager/pm-020.conf

You could set that file up with pretty much what you want. I believe
the latest version of portmanager has been released. You might want to
check on that.

I use portmanager as opposed to portupgrade myself. I find it does a
better job without using all sorts of switches on the command line.

Personally, I would run:

portsclean -C -D -L -PP

Then, if anything is still in the /usr/ports/distfiles directory, you
could just remove them manually. Then run 'portmanager -u' to finish the
job. Obviously, run cvsup tp update your ports immediately prior to
running either portmanager or portsupdate. The advantage with
portmanager is that it does not need an index file. You do not have to
either build a new one; i.e., portsdb -Uu or fetch one.

Just my 2¢

-- 
Gerard Seibert
gerard at seibercom.net



More information about the freebsd-questions mailing list