Rohan Dhruva wrote: > On 4/29/06, Tom K <[EMAIL PROTECTED]> wrote: > >> This comes up every now and then, and the answer is, as always, that the >> packages should be flagged out of date (python and openssl already are), >> and the devs will get to them when they get to them. If you're in a >> hurry, get the PKGBUILDs and any associated build files from CVS or ABS, >> and build them yourself. >> > > Thats exactly the reply I recieved. For gods sake, we *know* we can > modify PKGBUILD to get new version for ourselves. We are here > requesting the pkg to be updated in the _repo_ > >
And I am here saying that as it is already flagged, your request is unnecessary. >> Another thing - are we in a race here? Why would it be necessary to >> "stay ahead of them"? >> >> > > Isnt it arch's motto to stay bleeding edge up to date ? > > Point me to wherever that's written, and I will eat my words. Here's the closest I can find, on the Archlinux intro page in the wiki: "Arch Linux strives to maintain the latest stable version of its software." Note that word 'strives', which, when put in the Arch context, where there is a small dev team, working very hard in their spare time for no money, means that they will get to them when they get to them. Until we find some Shuttleworth clone to pump money and resources into Arch, that's the way it will work. IMO, the dedication of the dev team, along with extensive community involvement, means it works very well. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
