Prevent removal of configured files after Portfile change

[Simon Ruderich]

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

Ryan Schmidt wrote:
> I think you're saying that you have a port that installs a configuration
> file, and that you've then changed the configuration file, and when you
> upgrade the port, your changes to the configuration file are lost. The
> solution is for the port to install a *sample* configuration file, and
> for the user to manually copy the sample to the real configuration file
> name when configuring. See the apache2 portfile's httpd.conf.sample for
> an example.

Thanks for your answer, but I meant something else.
When I'm working on a new Portfile I often have to run for example the
"port -d configure" command very often, because some libraries are not
found and I have to experiment with the options (for configure).
But every time I change the Portfile it removes the old extracted data
and starts it all again. The same occurs with the "port -d build" command.
So my question is how can I prevent the removal of the files which were
extracted in the port's "work" directory.

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)

iD8DBQFGki4PYRX4BO+zMikRCtqDAJ9tbBHdfO/iA8Ypmux0YLTMF1RcwwCeNyZL
C/CwFhXNUjiTJ/i7ivbuc1g=
=+jqM
-----END PGP SIGNATURE-----