Max Horn wrote: > <sigh>. I am a bit tired of learning about changes to my packages only > after they've been made. At least you, Ben, take the time to inform me > about it -- thanks for that (honestly, no sarcasm intended). I > understand that you have the best intentions with that, of course. > However, in the end, while it's probably the quickest way to get the > 10.4 tree up and ready, it puts some work on me -- I have to review the > change, and understand it, and then decide whether and how I feed it to > upstream (in this case, the issue definitely deserves to be resolved in > upstream, but requires a very different solution, obviously).
I'm sorry to have annoyed you by doing this; if a change is significant enough I generally ask the maintainer first, but since this was an obvious one-liner, I figured it was OK to just apply it (and, in fact, it isn't even 10.4-related, I just happened to have run into it with some other stuff I was working on). > Now, I guess it is too much work / annoyance to send patches to the > maintainer first, letting them apply them (or a modified version) as > they deem appropriate. The problem here of course being that often those > maintainers may not react in a timely fashion -- having been in the very > same situation, I fully appreciate this difficulty. However, for those > package maintainer who *are* willing to quickly react on such > notifications (e.g. me), it is a bit hard to accept that their packages > are simply taken out of their hands :-/. Of course, in the end, you make > a patch for me, and the work I have to do is almost the same regardless > of whether I am told about it in advance or not -- but the feeling is a > quite different one. As it is, I feel like I am not in control of my own > packages anymore, but am left with the task of giving support for them > anyway. That's a very unsatisfying situation. I can understand your frustration; I will strive to be better about asking first... One day won't make a difference in the grand scheme of things. (On that note, mind adding --disable-sdltest to your sdl-image package(s)? The won't build on my remote box at the moment... <g>) I think the biggest issue is not even necessarily that it's a problem waiting for the maintainer to respond, generally you know who responds quickly and who doesn't. The thing is, if I'm making a bindist to see what works and what doesn't, I can either fix things, and try again, or I can send out 10 e-mails and now not only does the maintainer need to do something about it, but now I need to remember to go back and check on all those emails I sent out before. Personally, if I leave a little TODO like that, I've already forgotten it, and it doesn't get done, and I spend more time re-remembering it needs to be done later. :P I suppose I can change my workflow to put stuff on the wiki, that way at least I won't forget about it. -- Benjamin Reed a.k.a. Ranger Rick http://ranger.befunk.com/ ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
