I think we could ask users during installation whether they would want [community] enabled or not, and also throw in an appropriate warning. The value of this idea, I think, lies in the fact that the new user will be aware of [community]'s existence rather instantaneously.
regards, /K. --- Yi Qiang <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Hi, > > > > I do not remember this being discussed, so here I > go: > > > > a point of criticism has always been that Arch has > a lot of packages > > missing from the standard repositories. What about > including > > [community] by default in 0.8s pacman.conf? TUs do > their work diligently > > and new users could be offered a lot of packages > out of the box. > > > > We could also ask them at installation time > whether they want to enable > > it or not. > > > > Regards, > > > > Leslie (dejari) > > > I don't think that's a great idea for quality > reasons. I personally > feel that the packages in community/ are actually > quite usable, but > there's little guarantee that the packages always > work/do what they're > supposed to do. The TU's do a good job but unless > packages in community > go through further testing (i'm not even sure what > type of extended > testing those packages get now) I think it'd be > better to leave it out > of the default config. I think it would be great to > enable people to > add another repo at install time if they choose to > do that. > > Yi > > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
