Well, we certainly have a little bit of a thread going on here... Let me respond to a few things:
a) I agree the PHP5 thing was an issue, but it's an isolated incident (and, IIRC, it was the result of one developer being inactive and people bitching about the package not being up to dat, so another developer stepped in and updated it) b) As for Arch in production environments - Arch provides the perfect framework for production environments if you make sure to manage your own repo, and have a single test machine for official packages. It's not hard, and many many businesses test upgrades anyway. I know of no one who just downloads new versions of programs on their production machines on a whim - there's always a decent amount of testing. c) Patches - I have noticed alot more patches as of late. Packages that used to be as simple as "./configure && make && make install" are not patched 5-6 times. However, there is nothing anywhere in the arch "mission statement" that says patches are bad. In fact, the only thing I've heard on this topic was from the mouth of Jason, when he said "we try not to patch things unless they do not provide sane defaults" (paraphrased). d) As for the notification "channel", I see things like: "How about the front page?" - "Not everyone checks the front page" "Well, then, how about an RSS feed?" - "Not everyone has a feed reader" "How about forums/mailing list?" - "Not everyone reads those" Christ people, pick one. There will never ever be one medium which satisfies everyone. The devs have chosen to use the dev blog, which Jason so kindly linked to. If someone doesn't like this, then tough shit - deal with it. - phrak _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
