[90772] trunk/dports/_resources/port1.0/group/crossgcc-1.0.tcl
Aljaž Srebrnič
g5pw at macports.org
Wed Mar 14 02:48:58 PDT 2012
Ok, few things:
1) thanks for fixing whitespace. I have to remember to check indentation and whitespace before committing.
2) The problem with the extract.only keyword is that my msp430-gcc[-devel] ports download the full gcc archive (gcc-4.5.6, for example) and that breaks if extract.only is set like that.
Should I just override extract.only in my portfiles?
On 14/mar/2012, at 10:29, raimue at macports.org wrote:
> Revision
> 90772
> Author
> raimue at macports.org
> Date
> 2012-03-14 02:29:30 -0700 (Wed, 14 Mar 2012)
> Log Message
>
> group/crossgcc:
> Explain why extract.only is required here
> Modified Paths
>
> trunk/dports/_resources/port1.0/group/crossgcc-1.0.tcl
> Diff
>
> Modified: trunk/dports/_resources/port1.0/group/crossgcc-1.0.tcl (90771 => 90772)
>
> --- trunk/dports/_resources/port1.0/group/crossgcc-1.0.tcl 2012-03-14 09:21:48 UTC (rev 90771)
> +++ trunk/dports/_resources/port1.0/group/crossgcc-1.0.tcl 2012-03-14 09:29:30 UTC (rev 90772)
> @@ -84,11 +84,10 @@
>
> depends_build port:gettext
>
> - # I don't know why is this here, it looks redundant.
> - # macports should already extract all the distfiles!
> - #extract.only ${dcore} ${dcxx} ${dobjc}
> + # Extract gcc distfiles only. newlib tarball is available as gzip only;
> + # handled below in post-extract in the variant.
> + extract.only ${dcore} ${dcxx} ${dobjc}
>
> -
> # Build in a different directory, as advised in the README file.
> post-extract {
> file mkdir "${workpath}/build"
> _______________________________________________
> macports-changes mailing list
> macports-changes at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-changes
Aljaž Srebrnič
-- --
My public key: http://bit.ly/g5pw_pubkey
Aljaž Srebrnič
-- --
My public key: http://bit.ly/g5pw_pubkey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20120314/d77e9f3b/attachment.html>
More information about the macports-dev
mailing list