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