Date: Sun, 16 Sep 2012 06:30:49 -0400 From: Jerry <jerry@seibercom.net> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: apache 2.2.22_8 Message-ID: <20120916063049.6b866dbd@scorpio> In-Reply-To: <CADLo839g-hEBtcnYHH0eJCpaTWigLg=wqPzBcVy9tLRHDgLWJw@mail.gmail.com> References: <5054BB1D.4080506@celicom.ru> <CAAdA2WOzATez6MYJauKXVF6QOpn7kpDigG2m0G2=WF%2BK=mk2KQ@mail.gmail.com> <CADLo839g-hEBtcnYHH0eJCpaTWigLg=wqPzBcVy9tLRHDgLWJw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 16 Sep 2012 09:17:55 +0100
Chris Rees articulated:
> You need to use ${UNIQUENAME}_SET, and to find the UNIQUENAME you
> need to;
>
> [crees@pegasus]~% cd /usr/ports/www/apache22
> [crees@pegasus]/usr/ports/www/apache22% make -VUNIQUENAME
> apache22
>
> Now we know it's apache22, we can use:
I tried this with "postfix" and the "postfix-current" port and both
returned the same unique name. Is that to be expected? I would have
though that two different ports would return different unique names.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
The trouble with a lot of self-made men is that they worship their
creator.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120916063049.6b866dbd>