On Monday, December 16, 2002, at 07:19 PM, Patrick N�f wrote:
This would be useful, i think. But it would probably be easier to make you a fink developer and give you CVS access if you want to contribute all this work.
Before starting work I would make a final selfupdate-cvs and then put aside the whole 10.2 tree. I would then add the fields to the .info files, make a ball from the files for every maintainer and... do what? Send it to them personally? Put it on the package submission tracker?
Anyone making changes to fink info files should let the maintainer know, just as courtesy. And if its more than a very minor change you should ask first. Homepage and MD5 are probably ok to add for people. (though if its a "changing MD5" and not a "new MD5", you would want to figure out why its cahngi)
-Ben
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
