Matthew Seaman schreef:
Jerry wrote:
On Sat, 04 Apr 2009 13:46:11 +0100
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
I find it's also a good idea to add a warning about such things to
any pkg_message printed out at install time.
Thanks! I was considering the pkg_message idea;
I maintain a port that is undergoing some radical changes in the way it
maintains its 'config' files. This will require that the end user make
some minor changes in order to get the program to run correctly. How do
I go about getting something posted in the UPDATING file? I couldn't
find anything
Jerry wrote:
I maintain a port that is undergoing some radical changes in the way it
maintains its 'config' files. This will require that the end user make
some minor changes in order to get the program to run correctly. How do
I go about getting something posted in the UPDATING file? I couldn't
On Sat, 04 Apr 2009 13:46:11 +0100
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
Jerry wrote:
I maintain a port that is undergoing some radical changes in the way
it maintains its 'config' files. This will require that the end user
make some minor changes in order to get the program to
Jerry wrote:
On Sat, 04 Apr 2009 13:46:11 +0100
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
I find it's also a good idea to add a warning about such things to
any pkg_message printed out at install time.
Thanks! I was considering the pkg_message idea; however, users of
Portupgrade
On Saturday 04 April 2009 9:49:00 am Matthew Seaman wrote:
I find it's also a good idea to add a warning about such things to
any pkg_message printed out at install time.
Thanks! I was considering the pkg_message idea; however, users of
Portupgrade or other port maintenance tools often
