Hi Guido,
Nice sleuthing. I came to the same conclusion last night after
following up a similar report from another user.
I've written to Paul Guyot about the issue, who has the honor of
having written the changeset in question, but the blessing to not
have written the ugly hack that stumbled on it.
Hopefully we'll get this cleaned up soon. In the mean time, you can
turn off archive mode in your ports.conf file.
James
On Apr 20, 2007, at 4:00 AM, Guido Soranzio wrote:
An update to my previous report.
I think that the issue is due to the changeset 23238 and how
the new procedures command_exec and parse_environment in portutil.tcl
are managing the unarchive.env variable and the pipes.
With the release 1.4.0 of MacPorts, the assembled command was
'cd "/opt/local/var/db/dports/build/
_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_
dports_archivers_unrar
/work/destroot" && /usr/bin/gzip -d -c /opt/local/var/db/dports/
packages/darwin/powerpc/
unrar-3.7.4_0.powerpc.tgz | /usr/bin/tar -xvpf -'
With the latest sources, the content of unarchive.env (the gzip
command)
is missing from the pipe:
'cd "/opt/local/var/db/dports/build/
_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_
dports_archivers_unrar/
work/destroot" && /usr/bin/tar -xvpf -'.
_______________________________________________
macports-users mailing list
[EMAIL PROTECTED]
http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
