Questions about hardcoded rsync_path and svn_path

Simon Ruderich simon at ruderich.com
Thu Jul 12 11:56:01 PDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

today I had a problem that "port sync" wasn't working anymore. The
problem was that it used a rsync version which was removed by me.

I didn't knew that macports was using hardcoded paths and so had to
search for the offending configuration data.

After some time I thought I found it in this file:
${prefix}/share/macports/Tcl/port1.0/port_autoconf.tcl

I changed the values but it wasn't working. So I looked further and
found it here:
/Library/Tcl/macports1.0/macports_autoconf.tcl

So I have two questions about it:
1. Why is macports using hardcoded paths for this sort of values. I
tried just using "rsync" and it works.
2. Why are there two (configuration) files similar data.

I had some problems with macports hardcoded paths some time ago when I
tried to install multiple port installations. I never really fixed this
and have to rename my port installations to get it work.

Thanks for your help,
Simon
- --
+ privacy is necessary
+ using http://gnupg.org
+ public key id: 0x6115F804EFB33229
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFGlnlAYRX4BO+zMikRCpMyAKCuZtn/5shIB4KC+8sh+q1HFTsNJACePM5x
bSUwK8IzT+JggRQ+rIIM6IA=
=1X0O
-----END PGP SIGNATURE-----



More information about the macports-dev mailing list