ok, here's what I'd like to be added/modified to the current policy.txt. 2.4 SRC_URI > SRC_URI can contain multiple URLs. If you need different files > depending on the target arch, the syntax is: > SRC_URI="ppc? ( URL ) x86? URL" Ok, here we might provide a better example to show how portage is able to grab sources depending of USE settings. I.e. : ---- Since URLs in SRC_URI can depend on USE flags you can have somethink like: SRC_URI="http://cr.yp.to/${PN}/${P}.tar.gz ipv6? ( http://www.fefe.de/ucspi/ucspi-tcp-0.88-ipv6.diff11.bz2 ) ssl? ( http://www.nrg4u.com/qmail/ucspi-tcp-ssl-20020705.patch.gz )" ---- > URLs can be on the form http://, ftp:// or mirror://. The latter is > very useful for packages hosted on SourceForge. might specify the thirdpartymirrors and provide an example. ---- Moreover, URLs can be on the form http://, ftp:// or mirror://. The latter is very useful for packages hosted on SourceForge, GNU or KDE/GNOME related or CVS snapshots on gentoo.org FTP. Portage uses mirrors listed in /usr/portage/profiles/thirdpartymirrors. Here's an example: SRC_URI="mirror://sourceforge/kfilereplace/${P}.tar.bz2" ---- 2.8 Miscellaneous Variables (DESCRIPTION) trivial fix, DESCRIPTION is used in `emerge --searchdesc`, not `emerge search` 3.2 src_compile Please let's add that *econf is available*, it's defined in ebuild.sh and there's no need to add a '|| die "reason"' after it. Moreover, there's no need to specify src_compile AT ALL, if all it does is econf and emake. 3.3 src_install Again, let's specify that *einstall is available*, it's defined in ebuild.sh and there's no need to add a '|| die "reason"' after it. Then, let's specify there are einfo/einfon/ewarn/eerror, so there's no need to use stuff like echo -e "\e[32;01m .. I saw in LOTS of ebuilds. okay, I'll keep adding stuff here to improve ( I hope:) )the current policy. Thanks :) -- Maurizio aka j2ee
Fixed. New POLICY.txt uploaded.
