On Tue, 2005-12-06 at 09:23 +0100, Tobias Powalowski wrote: > Am Dienstag, 6. Dezember 2005 08:25 schrieb Benoit Chesneau: > > Hi, > > > > Just a talk. But it seems there are more and more patchs in pkgbuilds > > and this now very difficult to check packages or such things like > > customize a package for specific needs. At least if patchs would be > > documented it would be usefull. Anyway I thought that one principle of > > Arch Linux was simplicity and the less patch as possible. What is the > > position right now ? > > > > One other point I dislike is the the lack of transparency about upgrade > > or major changes in architecture like udev, initscripts, hal, kernel > > that we had in last months. This changes should be coumminicated before > > the release of the package, and package should be always tested before > > and put in testing to do it in my opininion. This last point should be > > for all packages. For example if we take php package we see 5 changes in > > 10 days and package is always updated in current.... That's shouldn't > > be... What about people that works with it... Not everybody coule be a > > tester everyday.... > > > > > > Anyway, archlinux stay the best distribution I've found for now, but I > > think these points should be solved to my mind. What do you think about > > it ? > > > > > > - Benoît > > Webmaster, http://archlinuxfr.org > > > > _______________________________________________ > > arch mailing list > > [email protected] > > http://www.archlinux.org/mailman/listinfo/arch > Hi > kernel and udev changes are done in testing atm, so i don't see a problem > here.
yes at least for these packages. But when a change have an impact on habits on the machine it should be explain. Like we don't need anymore hotplug or such thing like it.... Or hal that works well with last udev but when it was updated, udev wasn't .... This is kind of example that are very annoying.... Or prepare to inistcript changes before with a message on the site. I dislike the fact I have to see man after upgrade... In fact I dislike suprises on my pc. > The packages in testing are tested on developer pc's. > greetings this isn't enough to my mind... More over, in short, it seems it isn't enough: last hal, php packages and initscripts are an example.... A dev couln't test all problem. That's why all packages should be in testing before to be in current. A least one week, a month would be better. Regards. > tpowa > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
