From: David Relson <relson@osagesoftware.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [OT] Questions about building from source tarball
Date: Thu, 1 Nov 2012 23:33:44 -0400 [thread overview]
Message-ID: <20121101233344.2cf5d4d0@osage> (raw)
In-Reply-To: <20121101002910.GA29824@waltdnes.org>
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 <waltdnes@waltdnes.org>
> I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2012-11-02 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 8:56 [gentoo-user] [OT] Questions about building from source tarball Walter Dnes
2012-10-30 17:24 ` Michael Orlitzky
2012-10-31 0:26 ` [gentoo-user] " walt
2012-11-01 0:29 ` Walter Dnes
2012-11-02 3:33 ` David Relson [this message]
2012-11-02 9:14 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121101233344.2cf5d4d0@osage \
--to=relson@osagesoftware.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox