From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Old Firefox ebuild?
Date: Fri, 14 Oct 2016 21:38:43 +0100 [thread overview]
Message-ID: <20161014213843.3294ca7c@digimed.co.uk> (raw)
In-Reply-To: <20161014185747.10148.362D6CE8@matica.foolinux.mooo.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
On Fri, 14 Oct 2016 12:15:54 -0700, Ian Zimmerman wrote:
> I think this will work for me, thank you! However, I don't understand
> why those versions precisely are there (which means they have been
> checked into cvs, I guess) and not others? For instance, the exact
> version I'm running now, 38.8.0, is not there, and neither are the 45.x
> and up which already invaded my portage tree.
The ebuilds used to install existing packages are all in /var/db/pkg.
> > You could use 'emerge --buildpkg y' to build binary packages you can
> > revert to, in case an update/upgrade breaks anything important.
>
> Yes, and I should really learn more about binary packages in gentoo.
> But still, it isn't much different from listing the files with equery f
> and making a tarball.
The packages portage creates also contain package metadata, as stored
in /var/db/pkg
> Without a way to rebuild from source I feel as if
> I were standing on 1 leg ...
If you have the disk space, adding buildpkg to FEATURES will ensure you
always have a crutch available...
--
Neil Bothwick
Am I ignorant or apathetic? I don't know and don't care!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2016-10-14 20:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 18:02 [gentoo-user] Old Firefox ebuild? Ian Zimmerman
2016-10-14 18:16 ` Mick
2016-10-14 19:15 ` [gentoo-user] " Ian Zimmerman
2016-10-14 20:38 ` Neil Bothwick [this message]
2016-10-14 18:29 ` Holger Hoffstätte
2016-10-15 1:05 ` Ian Zimmerman
2016-10-15 3:27 ` Kai Krakow
2016-10-15 3:42 ` Kai Krakow
2016-10-15 5:35 ` [gentoo-user] Backup [Was: Old Firefox ebuild?] Ian Zimmerman
2016-10-15 8:14 ` Neil Bothwick
2016-10-15 19:22 ` [gentoo-user] " Ian Zimmerman
2016-10-15 21:03 ` Neil Bothwick
2016-10-26 18:40 ` [gentoo-user] transplant /usr/portage [Was: Backup] " Ian Zimmerman
2016-10-26 20:39 ` Neil Bothwick
2016-10-27 1:16 ` [gentoo-user] " Ian Zimmerman
2016-10-27 7:49 ` Neil Bothwick
2016-10-28 12:53 ` Fernando Rodriguez
2016-10-26 22:17 ` [gentoo-user] " Bill Kenworthy
2016-10-15 11:22 ` [gentoo-user] Backup " Rich Freeman
2016-10-15 19:18 ` [gentoo-user] " Kai Krakow
2016-10-14 18:39 ` [gentoo-user] Old Firefox ebuild? Alexey Mishustin
2016-10-15 23:41 ` Miroslav Rovis
2016-10-16 9:06 ` Alexey Mishustin
2016-10-14 18:40 ` Michael Mol
2016-10-16 10:34 ` [gentoo-user] " Martin Vaeth
2016-10-16 10:52 ` Alexey Mishustin
2016-10-16 18:08 ` waltdnes
2016-10-16 19:27 ` Martin Vaeth
2016-10-16 20:10 ` Miroslav Rovis
2016-10-17 0:04 ` Ian Zimmerman
2016-10-17 9:34 ` Wolfgang Mueller
2016-10-18 19:58 ` Ian Zimmerman
[not found] ` <CAHVfhucadA8hPT+T3B+PfQx36nG1NMCH5N6SyBWtWpsnm0SZJg@mail.gmail.com>
[not found] ` <CAHVfhud4-Mr+2K6c18xFTnonLuQhuO7VD5rHOS1pS+Oo8J+4+A@mail.gmail.com>
2016-10-19 4:41 ` Andy Mender
2016-10-21 12:10 ` Martin Vaeth
2016-10-21 13:09 ` Andy Mender
2016-10-21 17:14 ` Ian Zimmerman
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=20161014213843.3294ca7c@digimed.co.uk \
--to=neil@digimed.co.uk \
--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