In the past when I wanted/needed a newer version of a package than is in portage, I'd create an entry in /usr/local/portage.
For example for app-example/some-package/some-package.x.y.z.ebuild, I'd 1) create directory /usr/local/portage/app-example/some-package 2) copy some-package.x.y.z.ebuild to some-package.x.y.z-r1.ebuild (in the new directory). 3) Some editing of the new ebuild might be needed here... 4) Run "ebuild ... digest" on the new ebuild to create the Manifest file. 5) test with "ebuild ... compile" or "emerge some-package". 6) when errors are encountered, repeat steps 3, 4, and 5. HTH, David On Wed, 31 Oct 2012 20:29:10 -0400 Walter Dnes wrote: > Thanks for the pointer. It got me going... sort of. Now I know why > we don't have the latest seamonkey in the Gentoo tree. It requires > >=dev-libs/nspr-4.9.3 and the highest ebuild of nspr in the tree is > 4.9.2, even though I did an "emerge sync" today. So I'd have to build > nspr and nss locally from tarballs, and then set .mozconfig's > nspr-prefix and nss-prefix to the local copy... bleagh. I'll just > wait until nspr gets at least a keyworded 4.9.3 in the tree. > > -- > Walter Dnes <waltd...@waltdnes.org> > I don't run "desktop environments"; I run useful applications
