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 18:06:17 -0500	[thread overview]
Message-ID: <20150330230617.GB26091@crud> (raw)
In-Reply-To: <CAK2H+edgAzS+XAc8gdWspot_0RPo2D8ReHV3umW-mvsfQ78p9A@mail.gmail.com>

Mark Knecht <markknecht@gmail.com> skribis:
>    In my case I've been slowly converting my machine back to nearly
> 100% stable. I don't need anything more than that in my daily work
> these days and would greatly prefer fewer updates. In the old days
> when I ran a lot of Gentoo pro-audio overlay stuff I stay to stay
> leading edge all the time but these days I don't do that and life
> should be easier.

A few years ago I proved it is possible to go from ~amd64 to amd64 but
often I bump something to ~amd64 to overcome problems.

(For instance it turned out libav was being pulled in because the
~amd64 version of ffmpeg I had allowed was no longer in portage. I had
to bump the version.)

>    I was thinking back about my 32-bit usage when I built the machine.
> In those days (and it's likely still true) to run Windows VST plugins
> you had to have 32-bit support. I was doing a lot of software synth
> stuff a decade ago and suspect that was my main need in that area. I
> don't intentionally use 32-bit for anything so likely I don't need it
> at all as per Frank's comment but I also didn't feel like I really
> wanted to deal with that right now.

The processor is made to handle 32-bit so better to have it than not,
from my point of view. (The whole multilib thing might have gone
smoothly years ago, and with nomultilib a trivial difference, if we
merely had had the sense to stick with Gentoo’s original filesystem
layout for libraries. But this is my view in retrospect. We sometimes
pay a big price for following the leads of other distros.)


  reply	other threads:[~2015-03-30 23:06 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
2015-03-30 22:23       ` Mark Knecht
2015-03-30 23:06         ` Barry Schwartz [this message]
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=20150330230617.GB26091@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