Difference between pages "Idea Basket" and "Talk:Installsources"

(Difference between pages)
m (flag for deletion, old as the hills, unmaintained and issues about gentoo / old wiki & bug tracker.)
 
(Created page with "its content should be migrated to make.conf & then deleted.")
 
Line 1: Line 1:
{{delete}}
+
its content should be migrated to [[make.conf]] & then deleted.
 
+
The idea basket is a dumping ground for unclassified ideas.
+
 
+
* Compare merged files against in-use files to indicate what processes need to be restarted. This is particularly important for security updates since the outdated Apache will keep on running even if you update the on-disk binary. It needs to be restarted to be effective.
+
* Create a better issue-tracking/wiki integration.
+
* There were ideas for a portage-ng at one point: http://web.archive.org/web/20050404003507/http://www.gentoo.org/proj/en/portage/portage-ng/systemspec.xml
+
* Teach Portage about cross-compiling dependencies so it can bootstrap on its own. I think this could also do away with crossdev (which reportedly isn't working on Funtoo anyway) and would do away with special bootstrap scripts. As an example, compiling gcc with CHOST=i686-pc-linux-gnu, CBUILD=x86_64-unknown-linux-gnu, and ROOT=/x86_64-root should look in the package database on ${ROOT} for an appropriate binutils installation. If that is lacking, even if binutils is installed on the host, it will pull in binutils and cross-compile it appropriately for the other root.
+
* Teach Portage how to merge in all reverse dependencies of a package. That should address preserved-rebuild as well as revdep-rebuild types of issues.
+
* Teach Portage the types of CFLAGS that change ABI so it can rebuild system appropriately if an ABI-changing CFLAG is desired.
+
* Teach Portage about some sort of src_profile target so that compiler profiling can be used to make more intelligent optimization decisions.
+

Latest revision as of 14:43, December 1, 2014

its content should be migrated to make.conf & then deleted.