On Mar 21, 2006, at 03:00, Max Horn wrote:
Those batch updates usually involved adding a new field, or
replacing a dependency with a new one. I don't think that the
maintainers need to be notified & asked about this one-by-one.
However, a notification mail explaining the change in a generic
fashion ("We replaced the dependency on package XYZ with ABC and
UVW because of ...", which is sent to fink-devel (or, even better,
but probably far too much work for big changes, sent to all
affected maintainers), is IMO a must.
During the months leading up to Tiger's release, I did a lot of work
to get packages working on 10.4. My protocol for patching packages
was to notify the maintainers about the problem and ask them to fix
it, wait two weeks, ping maintainers who hadn't fixed the problem or
replied again, wait another two weeks, and then commit the changes
myself. Yes, this involved a lot of bookkeeping on my part, and some
patches fell through the cracks. And we had enough time before the
Tiger release that we could afford to wait a month for things to get
committed.
I developed the maintnotify script, in scripts/buildfink/, to help
with this. It takes a list of packages, a message template, and
optionally a directory which contains files named "foo.*" to include
as attachments for the notification for package foo.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
