As you see fit.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?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.
There's only one thing to consider: should the work be done quickly? If so then I will have to pass - unfortunately for fink my private life takes precedence.
On the other hand, if I can take my time with it (for instance, I will only be able to start the work until after Xmas), then yes, it would be a great pleasure for me to finally be able to make a contribution.
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)I only thought to add ***new*** MD5 sums where they are missing. Something along the lines of
find /sw/fink/10.2 -name *.info -exec fgrep -Hic source-md5 {} \; | grep :0$
I would group the work by maintainer and, when I have finished a group, send the maintainer an email with a list of what I added to which .info files. I think this should be appropriate.
Patrick
-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
