On Thu, 1 Nov 2012 23:33:44 -0400, David Relson wrote:
> 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...
Some files in the fi
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
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
On 10/30/2012 01:56 AM, Walter Dnes wrote:
Several years ago, back in the days of Mozilla 0.9x and Phoenix, I
used to build Mozilla and/or Pheonix from the source tarball.
Me too :) Every morning I'd pull from their source repo and build my own
and then file bug reports (there were thousand
4 matches
Mail list logo