the ebuilds are either masked or unmasked. those that are unmasked will install, and by default the latest unmasked one will install, ie if you go
emerge package and the latest unmasked version of package is 2.2.2-r1 then that will install. you can also ask for an earlier one like this: emerge =package-2.2.1 some packages are masked because they are regarded as unstable, ie not fit for general consumption. they may need more work to fit in100% with the gentoo system, or the package itself may not be ready for general release. You cannot tell that from the filename, you need to look inside. an unmasked x86 ebuild will have a KEYWORD of x86, a masked one will be marked ~x86. you can emerge the latest masked one by: ACCEPT_KEYWORDS="~x86" emerge package the numbering follows the author's numbering, so package-2.2.2.ebuild will install the author's 2.2.2 version of package. If the ebuild needs tweaking it will be renamed package-2.2.2-r1.ebuild. It installs the same version, but the ebuild will have changed to, maybe, set up something differently, apply a new patch, or whatever. Does that answer the question? On Thu, 01 Apr 2004 15:28:35 +1200 (NZST) [EMAIL PROTECTED] wrote: > It looks like they've got the 3.76 drivers there as well, or is it only the > e-builds with r1 in the version name that work? > > Quoting Nick Rout <[EMAIL PROTECTED]>: > > > and u can look at the ebuilds here, and suss out what they do. The > > current latest is ati-drivers-3.2.8-r1.ebuild > > > > http://linux.citylink.co.nz/gentoo-x86-portage/media-video/ati-drivers/ > > > > (they are text files so they may not open in the browser - depends on > > the browser and how it is set up) > > > > > > On Thu, 01 Apr 2004 14:49:02 +1200 (NZST) > > [EMAIL PROTECTED] wrote: > > > > > That looks like what the thread is talking about, although it does > > also mention > > > a patch for AMD processors as well - which may be there, but not > > included in > > > your excerpt. > > > > > > Quoting Nick Rout <[EMAIL PROTECTED]>: > > > > > > > The ebuild seems to do some patching for the 2.6 kernel series, > > heres > > > > an > > > > excerpt: > > > > > > > > if [ "`echo ${KV}|grep 2.6`" ] ; then > > > > > > > > einfo "applying fglrx-2.6-vmalloc-vmaddr.patch" > > > > patch -p1 < ${FILESDIR}/fglrx-2.6-vmalloc-vmaddr.patch > > > > > > > > maybe this already does what is necessary? > > > > > > > > On Thu, 01 Apr 2004 14:14:41 +1200 (NZST) > > > > [EMAIL PROTECTED] wrote: > > > > > > > > > I have found a howto for the ATI driver on the 2.6 kernel here: > > > > > http://www.rage3d.org/board/showthread.php? > > > > > s=2f1fda16fb42aad44bb69cdc345f61c7&threadid=33730800 > > > > > It does involve patching the driver but seems fairly straight > > > > forward. > > > > > > > > > > Quoting "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>: > > > > > > > > > > > Although, looking at the website it appears that they are for > > the > > > > 2.4 > > > > > > kernel... > > > > > > and I would like to go to the 2.6 kernel if possible. > > > > > > > > > > > > Quoting "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>: > > > > > > > > > > > > -- > > Nick Rout <[EMAIL PROTECTED]> > > > > -- Nick Rout <[EMAIL PROTECTED]>
