On Dec 16, 2007 2:09 AM, Walter Dnes <[EMAIL PROTECTED]> wrote: > Do you have a list of significant improvements you want implemented? > There were gaping holes in linux's abilities in the past. These > problems have been fixed. Change simply for the sake of change is a > relic of the Windows era.
Ya, but let me remind you that Gentoo did not reach the perfect stage of "nothing more can be done to improve it". IMHO, there is one major project that Gentoo should start. Gentoo is a distro -I don't remember who told us Gentoo is not a distro, but it is- because there is something called portage tree. It is not just an LFS with a package manager (to do that, please read http://www.linuxfromscratch.org/lfs/ and install a portage tarball), because Gentoo provides thousands of packages that are maintained by gentoo devs. No more confusion, Gentoo IS a distro. Well, Grant -among others- is wondering about Gentoo future, and some difficulties that Gentoo currently faces. I love the efforts of some gentooers to claim that everything is okay in Gentoo world, they may skip the goodbye posts of all the leaving developers on the dev list, or may ignore the understaffed teams, but .... well, Grant, you are not stupid to wonder about future and your questions are not silly. Some improvement that can be done ? Someone reports difficulties for non-dev to become official dev or contribute. I think about something that EVERY linux distro lacks today. I am dreaming about a clear package tree representation. I mean, there is http://packages.gentoo.org/ for users to know which package are at disposal on which architectures, and so on. Let's imagine what a distro web site should provide... (not only on the web site but also integrated into the pkg management software) the categorized packages list, with search features of course, with ALL the information attached to each package, like the needs for maintainers as an example. There is neither announcements about the future ebuild releases, nor the Gentoo policy about this package... I think that this kind of information can be a good interface between official devs and the community to encourage new people to become devs, or to simply provide a better view on the current status of the portage tree and the near future. The package maintenance is a really hard task that requires lots of resources. OK. But there is a lack of resources. Is there actually nothing to do ? Is the automation of the package built with all USE flags combination and tests already done ? Are you sure that there is no process improvement possible (about the non-regression tests delivered with ebuilds) ? There is just one point on which I am sure .... it is hard for non-dev to know how things turn on. Gal' -- [EMAIL PROTECTED] mailing list
