On 07/08/2012 20:30, Jeremy Chadwick wrote:
So it's based off of UNIQUENAME? That's interesting.
The documentation implies that the name of the variable itself
should be the {nameofport}_SET or {nameofport}_UNSET, where {nameofport}
should equal the name of the actual port directory you're
On 08/08/2012 07:25, Matthew Seaman wrote:
Actually, that raises an important point, because the constructed
variable names like 'mysql55-client_SET' should perhaps have
syntactically significant characters like '-', '+' mapped to '_'
Interesting. A very quick test shows that make(1)
On 08/07/2012 11:53 PM, Matthew Seaman wrote:
On 08/08/2012 07:25, Matthew Seaman wrote:
Actually, that raises an important point, because the constructed
variable names like 'mysql55-client_SET' should perhaps have
syntactically significant characters like '-', '+' mapped to '_'
On 2012-08-06 18:04, Jeremy Chadwick wrote:
(Please keep me CC'd, as I'm not subscribed to the list)
I've been trying to adapt my /etc/make.conf to make use of the new
OPTIONS framework. I've run into some snags that I was hoping someone
could help me with, as I'm unable to find any
On Tue, Aug 07, 2012 at 08:43:18PM +0200, Olli Hauer wrote:
On 2012-08-06 18:04, Jeremy Chadwick wrote:
(Please keep me CC'd, as I'm not subscribed to the list)
I've been trying to adapt my /etc/make.conf to make use of the new
OPTIONS framework. I've run into some snags that I was
On 2012-08-07 21:30, Jeremy Chadwick wrote:
On Tue, Aug 07, 2012 at 08:43:18PM +0200, Olli Hauer wrote:
On 2012-08-06 18:04, Jeremy Chadwick wrote:
(Please keep me CC'd, as I'm not subscribed to the list)
I've been trying to adapt my /etc/make.conf to make use of the new
OPTIONS framework.
(Please keep me CC'd, as I'm not subscribed to the list)
I've been trying to adapt my /etc/make.conf to make use of the new
OPTIONS framework. I've run into some snags that I was hoping someone
could help me with, as I'm unable to find any official documentation
other than these two documents,
On Mon, 6 Aug 2012, Jeremy Chadwick wrote:
(Please keep me CC'd, as I'm not subscribed to the list)
2. ports/KNOBS is very explicit in stating, and even visually
demonstrating (using pipe symbols to delimit length maximums and so
on), the following:
# - Knob description must be 45 characters
On 8/6/2012 11:04 AM, Jeremy Chadwick wrote:
2. ports/KNOBS is very explicit in stating, and even visually
demonstrating (using pipe symbols to delimit length maximums and so
on), the following:
# - Knob description must be 45 characters or less
Yet, a very good number of descriptions
