On Aug 24, 2013, at 11:38, [email protected] wrote:
> Revision: 110016
> https://trac.macports.org/changeset/110016
> Author: [email protected]
> Date: 2013-08-24 09:38:17 -0700 (Sat, 24 Aug 2013)
> Log Message:
> -----------
> macports1.0: restore ability to install from a remote URL (binary archive or
> tarball of the port dir) removed in r109659
>
> Adds more documentation, cleanup code and progress information for the
> download.
> Modified: trunk/base/src/macports1.0/macports.tcl
> ===================================================================
> --- trunk/base/src/macports1.0/macports.tcl 2013-08-24 16:35:40 UTC (rev
> 110015)
> +++ trunk/base/src/macports1.0/macports.tcl 2013-08-24 16:38:17 UTC (rev
> 110016)
> @@ -1393,30 +1393,53 @@
> }
> }
>
> +##
> +# Extracts a Portfile from a tarball pointed to by the given \a url to a path
> +# in \c $portdbpath and returns its path.
> +#
> +# @param url URL pointing to a tarball containing either a file named \c
> +# Portfile at the root level -- in which case the tarball is
> +# extracted completely, -- or a file named \c +CONTENTS at the
> root
> +# level (i.e., the archive is a valid MacPorts binary archive), in
> +# which case the Portfile is extracted from the file \c +PORTFILE
> +# and put in a separate directory.
> +# @param local one, if the URL is local, zero otherwise
> +# @return a path to a directory containing the Portfile, or an error code
I'm curious about the backslashes ("\a", "\c") -- is that intended, or is that
some macro that was supposed to be expanded?
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
