public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@primate.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Old Firefox ebuild?
Date: Fri, 14 Oct 2016 12:15:54 -0700	[thread overview]
Message-ID: <20161014185747.10148.362D6CE8@matica.foolinux.mooo.com> (raw)
In-Reply-To: <1956864.9l4Pdrdm7X@dell_xps>

On 2016-10-14 19:16, Mick wrote:

> > Does anyone have a copy of the firefox 38.x ebuild around?
> 
> https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/firefox/

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.

> 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.  Without a way to rebuild from source I feel as if
I were standing on 1 leg ...

-- 
Please *no* private Cc: on mailing lists and newsgroups
Personal signed mail: please _encrypt_ and sign
Don't clear-text sign: http://cr.yp.to/smtp/8bitmime.html


  reply	other threads:[~2016-10-14 19:16 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   ` Ian Zimmerman [this message]
2016-10-14 20:38     ` [gentoo-user] " Neil Bothwick
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=20161014185747.10148.362D6CE8@matica.foolinux.mooo.com \
    --to=itz@primate.net \
    --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