[MacPorts] PortfileRecipes modified

[Ryan Schmidt]

On Mar 24, 2013, at 15:44, MacPorts <noreply at macports.org> wrote:

> Page "PortfileRecipes" was changed by larryv at macports.org
> Diff URL: <https://trac.macports.org/wiki/PortfileRecipes?action=diff&version=60>
> Revision 60
> Comment: update default GCC variant; add gcc48; remove some line breaks
> Changes:
> -------8<------8<------8<------8<------8<------8<------8<------8<--------
> Index: PortfileRecipes
> =========================================================================
> --- PortfileRecipes (version: 59)
> +++ PortfileRecipes (version: 60)
> @@ -307,54 +307,51 @@
> 
> == Providing compiler variants == #gcc
> 
> -By default, a port will compile using Apple's gcc compiler.
> -For most ports this is fine, but some require a newer version of gcc, or are for some reason incompatible with Apple's version.
> -In these cases you can use `configure.compiler` to specify an alternate compiler, for example one provided by a MacPorts gcc port.
> -More commonly, a port specifies such a compiler because it needs gcj or gfortran, which Apple does not provide any version of at all.
> -Another reason to want compiler variants is if the software installs a library, or uses a library built with a different gcc.
> -Subtle and difficult-to-find errors can occur if a library and the program using it are not both compiled with the same compiler.
> -
> -So on the one hand, all such ports should default to using a particular common version of gcc; the version we are currently using as the default version in MacPorts is gcc45.
> -On the other hand, a user may want to use a different gcc version.
> -Therefore, ports that need to use a gcc port, but aren't picky about exactly which one, are encouraged to offer variants:
> -
> -{{{
> -variant gcc43 conflicts gcc44 gcc45 gcc46 gcc47 description {Compile with gcc 4.3} {
> +By default, a port will compile using Apple's Clang or GCC compiler. For most ports this is fine, but some require a recent version of GCC, or are for some reason incompatible with Apple's version. In these cases you can use `configure.compiler` to specify an alternate compiler, for example one provided by a MacPorts GCC port. More commonly, a port specifies such a compiler because it needs GCJ or GFortran, which Apple does not provide. The software may also install a library or use a library built with a different GCC; subtle and difficult-to-find errors can occur if a library and the program using it are not both compiled with the same compiler.
> +
> +So on the one hand, all such ports should default to using a particular common version of GCC; the version we are currently using as the default version in MacPorts is `gcc47`. On the other hand, a user may want to choose their GCC version. Therefore, ports that need to use a GCC port, but aren't picky about exactly which one, are encouraged to offer variants:

It's by no means a big deal, but the linebreaks were there on purpose, so that if you add or remove or modify a sentence in a paragraph, the corresponding diff is relatively short and clear. When you have a single 655-character-long paragraph, like we now do here, that means any change to any part of that paragraph will show up in the diff email as a change to the entire paragraph, and it will be difficult to see from the diff what change was made, and this makes spotting errors more difficult.

Also, your diff above has combined changes to the substance of the document with whitespace changes, so that it's difficult to see from the diff what the substantive changes are.