Sorry, meant to send it to list...
On 9/8/06, Stefan <[EMAIL PROTECTED]> wrote:
Subject: ports management, update, flavors & co
Hi,
I have some basic questions about managing the ports tree.
1) Is the favoured way to upgrade the installed ports still like this:
cd /usr/ports && make index
cd /usr/ports/infrastructure/build && sh out-of-date
I couldn't find any information about upgraden the ports. I found a
lot of infos about updating the ports tree via cvs but not how to
upgrade the installed ports when a new version comes out.
2) Is it even possible to update only certain ports? Like you have a
port xyz installed and you only want to update this specific port.
Can you switch to /usr/ports/abc/xyz and do a "make update" to check
if a new version is out?
No, those two work the other way around than you think.
/usr/ports/infrastructure/build/out-of-date only checks and notifies
you of new ports available (and the ones that depend on it that should
be recompiled), and "make update" in port's dir makes it compile and
reinstall the new version.
3) Some time ago I used FreeBSD as my main server system and there
you had to specify the compile options (in OpenBSD you say FLAVOR'S)
in /etc/make.conf. There you could specify e.g. that the package xyz
should be compiled with the option "no_x11". In OpenBSD you do this
via "env FLAVOR=no_x11 make install". But what will happen when you
upgrade the port? Then you won't specify the flavor again. How does
the ports-system handle this?
I tried something like this:
/etc/mk.conf:
.if ${.CURDIR:M*/net/jabberd*}
FLAVOR=db
.endif
But this doesn't work the package will be compiled with the default
flavors.
No, you leave mk.conf alone (at least for that purpouse). "cd port/dir
&& FLAVOR=no_x11 make update clean-depends" is the way to go.
(clean-depends so you don't have the unpacked sources and compiled
binaries unnecessarily lying around)
Any suggestions, hints or whatever would be fine ;-)
Best regards,
Stefan
--
viq
