Richard Golier wrote:
What to do if packagers don't update their pkg even after they've been flagged
as out-of-date for a long time? As an example take links: Last Updated:
2005-04-04, ok i contacted dorphell on irc and let him know, but still no
update.
Or bluefish Last Updated: 2005-07-09. There have been 2 new versions since
then, pkg is flagged out-of-date and still nothing...
Are the maintainers so busy? I understand they may have a lot of work, but
replacing pkgver in PKGBUILD and compiling both of the packages took me about
3 minutes, so it's not that time-consuming.
I have one response to this. Not a criticism either way, but more a
sharing of additional information.
For one, sometimes developers are that busy. As we all know, the cost of
"task switching" can often be one we sometimes can't afford -- even for
a task that only takes a few minutes. Turns out my inbox is filled with
about 100 tasks that take 5 minutes right now.. so how do I prioritize?
The answer is that work has been really busy lately, and I can't afford
to do any of those 5 minute tasks, so none of those is getting done
right now. Maybe next week.
For two, replacing a pkgver in a PKGBUILD and compiling isn't where it
ends for a developer. One of the key things a developer must/should do
is TEST, at least basically, each version they release.
Bugs/incompatibilities get introduced into things all the time. Each
version of squirrelmail or motion I release, for example, sits on one or
two of my own production servers for testing for at least a day or two
(but usually a week) before I release it. This is what guarantees
quality releases for all of you out there.
Just trying to add some more perspective that might help you understand
why you haven't seen an update yet.
- P
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
