I think it's slowly getting time to think about the requirements for Gentoo v1.0. Implementing those will make it possible to do a feature freeze and iron out all outstanding bugs. Please add your comments / vision on what should and shouldn't be there to make things advance.
Portage 2.0 is imho a very important requirement. Portage is the center of the entire distribution and it should be clean to start v1.0 with. A lot of little userfriendlyness features should be added to smoother out the edges.
Agreed, it might also be time to start thinking of either freezing thee portage tree and only allow security updates or updates for brooken packages or to branch and start working on getting everything in the 1.0-branch to build perfectly.
Deciding which packages will be inside 1.0 and which not is also important. Updating old packages to the latest ebuild specs should also be done.
a descision on eclasses needs to be taken pretty soon.
Developer and portage documentation should be updated.
A document describing how and where Gentoo is different from other distribs might be handy for people who are switching
We need a new smarter more convenient USE system and a rewrite of the downloader in Portage ("resume" support)
is resume a problem with wget or within portage?
Following are the portage fixes/additions that have been agreed upon for Gentoo v1.0 : 1) USE toggles: USE="+gtk"; USE="-alsa" 2) auto-USE: each USE var can have a set of dependencies. We have an OPTION="" var to turn on "auto-use if dep satisfied"(based on deps being satisfied) 3) external category definitions 4) SYNC variable 5) download reimplementation with resume 6) binary compatibility slot: install as /var/db/pkg/cat/${PN}-${SLOT} where slot is by default ${PV} (ensures that for every version, only one rev will exist by default)
*** Bug 205 has been marked as a duplicate of this bug. ***
binary compatibility slots have been implemented
Hi! A simple one. The addition of a FFLAGS variable in /etc/make.conf and /etc/make.globals so users can specify.
what if FFLAGS used for?
FFLAGS the standard ENV variable for compiler options when using g77 (or any other fortran compiler for that matter) They are analogous to CFLAGS and CXXFLAGS. Would be useful for ebuilds that have fortran in the source. Currently I have either been hardcoding sane and or recommended defaults or just letting the defaults in the Makefile stand. Example ebuilds for packages having all or part of the source in fortran are dev-lang/R dev-lang/octave In fact you might be suprised (I was) at which packages would use FFLAGS, I just 'grep -Hr FFLAGS /var/tmp/portage/*' and gnome-python and sylpheed pooped up (wouldn't have figured :)
Tod, send me some good FFLAGS. Should they be the same as CFLAGS?
Hi! I was afraid somebody would ask me that :) I would hazard to suggest the following for a reasonable optimization default assuming that x86 is the only cpu architecture Gentoo will support in the near future. Most FORTRAN flags tell g77 how to compile for the FPU and depends on the architecture and which IEEE floating point calculation standards it conforms to. FFLAGS="-march=<arch> -O3 -pipe -malign-double -funroll-loops" The first three are the standard flags currently used, i.e. CFLAGS and CXXFLAGS. The -malign-double (Note: specific to x86 processors *only*) and -funroll-loops (only "DO" loops) flags are especially applicable to FORTRAN programs. These are the only two flags mentioned that improve performance in general. The other flags only *might* improve performance depending on the code and cpu architecture. A complete listing of compiler flags useful for FORTRAN can be found at http://gcc.gnu.org/onlinedocs/gcc-2.95.3/g77_9.html#SEC18 or, alternatively, the analogous node in 'info g77' I wouldn't characterize myself as an expert on FFLAGS. If someone else has comments or suggestions, I would be interested in hearing them.
Concerning optimization flags, I did some poking around and found some interesting information. First an article on Linux Journal: http://www.linuxjournal.com//article.php?sid=5886 which referenced "Securing and Optimizing Linux" http://www.linuxdoc.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/gen-optim.html 6.1. The /etc/profile file, has recommended flags, but the next few sections after have interesting benchmark results. But it turn out all this info is derived from the http://gcc.gnu.org/benchresults/ Pretty graphs are found at http://gcc.gnu.org/benchresults/cov.html which breaks out benchmarks by C++, FORTRAN, etc. It is interesting how the recommended optimization flags change subtly going from i486 --> i586 --> i686
perhaps a LDFLAGS would be nice? (See KDE-thread in gentoo-users about performance) reasonable (?) would be -z combreloc
