-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
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
On 09 Jul 2007, at 14:46, Simon Ruderich wrote:
-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
On Jul 5, 2007, at 2:04 PM, Landon Fuller wrote:
My own (potentially unpopular) opinion is that this is possible to
implement and impossible to support, as it would introduce
exponential complexity to the dependency tree.
I agree. The current workarounds for this lack of functionality
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Yves de Champlain wrote:
you mean port -o (as seen in the manpage)
yves
That's working, thanks for your quick response.
Stupid of me not trying it, but the manpage comment was a bit confusing
to me. But I just should have tried it.
Thanks
Hello,
Attached is a Portfile for flagpoll https://
realityforge.vrsource.org/view/FlagPoll . Please let me know if there
is anything else that needs to be done for its inclusion in MacPorts.
Thanks.
Doug
Portfile
Description: Binary data
Error updating macports from 1.5.0-rc1 to 1.5.0:
Getafix:~ rhwood$ sudo port selfupdate
MacPorts base version 1.5 installed
Error: /opt/local/bin/port: selfupdate failed: couldn't open /opt/
local/var/macports/sources/rsync.macports.org/release/base/config/
mp_version: no such file or
