Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Nov 2010 12:25:08 -0600
From:      Adam Vande More <amvandemore@gmail.com>
To:        Chris Brennan <xaero@xaerolimit.net>
Cc:        Dave <dave@g8kbv.demon.co.uk>, freebsd-questions Questions list <freebsd-questions@freebsd.org>
Subject:   Re: new user questions. (Before I back myself into a corner!)
Message-ID:  <AANLkTik6MvPHtuucSihG-pxPZQ0n1vxb8=KaBj0q6wnx@mail.gmail.com>
In-Reply-To: <AANLkTikRxZGOt5ZWXTLAt9d%2BmDz0vv-fLvxqm1XgxihX@mail.gmail.com>
References:  <4CED8855.23373.40E2965D@dave.g8kbv.demon.co.uk> <4CF13A7E.9852.186FE1D@dave.g8kbv.demon.co.uk> <AANLkTimt7uoZtRTEN-qeLC=BHe0yiPwAE=f5OzdSdpG=@mail.gmail.com> <4CF142A1.1231.1A6C687@dave.g8kbv.demon.co.uk> <AANLkTikRxZGOt5ZWXTLAt9d%2BmDz0vv-fLvxqm1XgxihX@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 27, 2010 at 12:05 PM, Chris Brennan <xaero@xaerolimit.net>wrote:

> No need to specify the full path w/ portmaster ... just "portmaster
> --no-confirm -D sysutils/tmux" is sufficient, portsnap is the best/easiest
> way to get the latest snapshot of ports. No real reason not to unless your
> using a custom ports or are maintaining your own ports and don't want them
> clobbered.
>

There are a couple of reasons specifying the full path is more convenient:

1.  tab-completions work
2.  When dealing with system utilities like whereis(1), the full path is
displayed making double-click+middle click give you correct cmd

portmaster $FULL_PATH - $PORTSDIR is only useful for me in cases where I
remember exactly where the port lives.

-- 
Adam Vande More



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTik6MvPHtuucSihG-pxPZQ0n1vxb8=KaBj0q6wnx>