Prevent removal of configured files after Portfile change
Simon Ruderich
simon at ruderich.com
Mon Jul 9 08:51:24 PDT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Emmanuel Hainry wrote:
> When I have to tweak with the configure arguments or build
> environment, I do that manually instead of relying on port: going
> inside the build dir and trying configure, make, even make install
> (with special prefix) in order to get a working process. Only after
> that do I write the Portfile and try trace mode to check for
> dependencies. There is no use in writing a portfile for something you
> are not sure will compile... Unless if you are able to guess
> everything in two tries and write patchfiles directly.
>
> Emmanuel
I'm using this approach too, but after I got it working with configure,
make, make install it sometimes doesn't work with macports instantly;
there are still some additional information (for example to configure)
necessary. And it speeds me up, when macports isn't removing the hole
directory (but thanks to Yves I know now how to prevent this).
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)
iD8DBQFGkll8YRX4BO+zMikRCu6qAJ4jv66tV6sUo/3jBFYFhVtNUMnKqQCguF/D
ZE4fiDx4XoPFfbJRzkPevIU=
=HIE6
-----END PGP SIGNATURE-----
More information about the macports-dev
mailing list