[90393] trunk/dports/lang/sbcl/Portfile

Mark Evenson evenson at panix.com
Mon Mar 5 02:08:55 PST 2012


On 3/4/12 22:51 , Ryan Schmidt wrote:
>
> On Mar 4, 2012, at 07:11, easieste at macports.org wrote:
>
>> Revision: 90393
>>           http://trac.macports.org/changeset/90393
>> Author:   easieste at macports.org
>> Date:     2012-03-04 05:10:59 -0800 (Sun, 04 Mar 2012)
>> Log Message:
>> -----------
>> lang/sbcl: passes port lint and human inspection of output.
>
> I pick further nits! See below.

[…]

> Whereas before it was stored as a single line, and MacPorts was able to introduce line breaks in the correct places, regardless of terminal width:

The terminal output seems to wrap the text in funny places for me.

I guess that a string literal enclosed via "{" and "}" is quite a bit 
different from one not somehow.

I took another whack at fixing things in [r90432]()

[r90432]: http://trac.macports.org/changeset/90432

[…]

> We don't manually add wording like "Enabled by default" to variant descriptions; MacPorts automatically indicates which variants are enabled by default when you use the default_variants command. For example the pango port:
>

[…]

> The "[+]" before the x11 variant indicates that it is a default variant of the port and will be automatically selected. (The "(+)" before the universal variant indicates that it will also be automatically selected, but only because I have placed "+universal" into my variants.conf file.)

[…]

> In the case of sbcl, it does not appear as though the threads variant is actually enabled by default. If you want it to be, add the line "default_variants +threads".

Ooh. That explains things.  I'll do that (make threads the default) in a 
subsequent commit, as it is certainly quite stable at this point.

-- 
"A screaming comes across the sky.  It has happened before, but there
is nothing to compare to it now."


More information about the macports-dev mailing list