public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Did devs change phonon flags without rev'ing package?
Date: Mon, 30 Mar 2015 17:10:33 -0500	[thread overview]
Message-ID: <20150330221032.GA26091@crud> (raw)
In-Reply-To: <CAK2H+edUiBxrHzyqKUOf6NGYuXz9zBi+cev5Uo_ok1VVDqvAWw@mail.gmail.com>

Mark Knecht <markknecht@gmail.com> skribis:
> On Mon, Mar 30, 2015 at 2:04 PM, Frank Peters <frank.peters@comcast.net> wrote:
> > On Mon, 30 Mar 2015 12:15:55 -0700
> > Mark Knecht <markknecht@gmail.com> wrote:
> >
> >> Yesterday I was emerge -DuN @world clean. It took hours due to Gentoo
> >> decisions about multilib stuff.
> >>
> >
> > Is it still necessary to be using multilib?
> >
> > I've been using pure AMD64 for so long I tend to forget that
> > 32-bit stuff still exists.
> >
> > Frank Peters
> 
> Hi Frank,
>    Honestly, I really don't know and figure the answer is probably no,
> but it was when I set the machine up this way 5 or so years ago. Even
> today I still see messages from things like Virtualbox drivers saying
> they are using 32-bit modes, but what do I know? When emerge threw all
> this stuff at me Sunday I figured I had no reason to break a machine
> that has been working well so I let it do everything it wanted to do.
> I don't have any problems with them getting rid of emulation libraries
> and having everything built into the packages. I just wasn't prepare
> for the time it required yesterday.

I’m still working on it, myself. Various problems. Nothing I won’t be
able to figure out. My list of things to build ~amd64 instead of amd64
is growing a bit, for instance. Had to fix one of my overlay
ebuilds. Etc. Removed some 32-bit stuff at least temporarily. I do not
use 32-bit stuff very often.

The main problem at this case is emerge wanting to install libav
despite that I’m set up for ffmpeg. These things happen.

At least if you use emerge as your package manager, it’s probably safe
to go ahead and uninstall the emul packages, if you haven’t. The
binaries will stay in place until you build the replacements.


  reply	other threads:[~2015-03-30 22:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 19:15 [gentoo-amd64] Did devs change phonon flags without rev'ing package? Mark Knecht
2015-03-30 19:48 ` Volker Armin Hemmann
2015-03-30 21:04 ` Frank Peters
2015-03-30 21:26   ` Mark Knecht
2015-03-30 22:10     ` Barry Schwartz [this message]
2015-03-30 22:23       ` Mark Knecht
2015-03-30 23:06         ` Barry Schwartz
2015-03-31  5:02   ` [gentoo-amd64] " Duncan
2015-03-31  7:32     ` Frank Peters
2015-03-31 16:40     ` Barry Schwartz
2015-03-31 19:43       ` David M. Fellows
2015-04-01  0:28         ` Duncan
2015-04-01  0:47           ` I can run 32-bit stuff and you can't (was Re: [gentoo-amd64] Re: Did devs change phonon flags without rev'ing package?) Barry Schwartz

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=20150330221032.GA26091@crud \
    --to=chemoelectric@chemoelectric.org \
    --cc=gentoo-amd64@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