installing ports xorg
mel.flynn+fbsd.questions at mailing.thruhere.net
Mon Mar 23 06:18:03 PDT 2009
On Sunday 22 March 2009 07:04:14 Glen Barber wrote:
> On Sat, Mar 21, 2009 at 10:20 PM, Tim Judd <tajudd at gmail.com> wrote:
> > I'm getting ZERO feedback when I install the xorg metaport, updated
> > ports tree today.
> > # cd /usr/ports/x11/xorg
> > # make install
> > #
> > So what am i missing?
> If xorg is already installed, you won't see any output. This is
> "expected" behavior, as far as I can tell.
No. This is expected behavior if make -V INSTALL_COOKIE -C /usr/ports/x11/xorg
exists, which can happen if:
1) You installed xorg on this machine and didn't make clean afterwards and now
try the install again.
2) You have /usr/ports mounted via nfs or nullfs from another machine or the
host system in a jail and have not set WRKDIRPREFIX. You installed xorg on
this other machine or the host system and did not make clean.
3) You have WRKDIRPREFIX set and that directory is mounted via nfs/nullfs.
Same applies as in 2)
4) You or some software ran:
touch `make -V INSTALL_COOKIE -C /usr/ports/x11/xorg`
> What happens on 'make
> deinstall; make fetch-recursive; make install' ?
This can be bad as deinstall will only delete the install and package cookie.
In other words, it will reuse the build and configure. If you were expecting
to upgrade your port, then this has unexpected results, especially with meta
In 90% of the case you will want to run make clean. Only if you want to reuse
a build you've done (for jails or on other machine, with same architecture and
OS version), you can use deinstall.
However, deinstall relies on /var/db/pkg, specifically if pkg_info cannot find
the port, it will be assumed it's not installed. It will go ahead and install
then, which can leave your installed ports with multiple versions of the same
More information about the freebsd-questions