Prevent removal of configured files after Portfile change

[Yves de Champlain]

Le 07-07-09 à 08:46, Simon Ruderich a écrit :

> -----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.

you mean "port -o" (as seen in the manpage)

yves