>A package should *always* call a specific version of automake. I would disagree. That would make migration to a new automake a royal PITA. Out of the 220 packages I'm watching, only 2 broke. Can you imagine the amount of maintenance if all 220 packages needed to be updated so any call to automake18 was changed to automake19? Basically, what I was aiming to do is let anyone building know that there is known breakage. Alan put both patches into cvs yesterday, so any further problems will be in the X windows packages AFAICT. The new packages are publicly available now. >The automake binaries are versioned for a reason - so installing a new >version doesn't break builds. They are versioned because the maintainers haven't made the adjustments to use the newest automake. I use the word maintainers in a broad sense. Both upstream and within the community. I have made such adjustments to the packages that I'm maintaining so that I could jettison those obsolete versions. Its not that hard to migrate the packages. You just need the will to do it. I'll feed some of those patches to Alan. -Steve Grubb __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail
