On Jun 23, 2004, at 9:38 AM, Jean-François Mertens wrote:
Update of /cvsroot/fink/dists/10.3/unstable/main/finkinfo/utils In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv408
Added Files: rpm.info rpm.patch Log Message: from 10.2-gcc3.3
I just got a bug report about this package in 10.3, before I was aware that it was actually in the 10.3 distribution. I found myself scrambling through fink-commits to figure out what happened. While I very much appreciate when folks help me out by checking my packages, I'd like to find out before getting bug reports. (I don't find fink-commits satisfactory for that, as there are too many messages for me to catch every one that pertains to me.)
I also see developers getting caught occasionally when BuildDepends are added to their package in CVS by someone else. Some developers make the next revision from a local .info file, rather than the CVS one, and so the BuildDepends are lost in the future. This should happen less if developers know when changes have been made.
Could we establish as policy that changes to another developer's package require that the developer be notified (or consulted before) either by e-mail or in fink-devel?
Dave
PGP.sig
Description: This is a digitally signed message part
