public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: gevisz <gevisz@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
Date: Sat, 16 May 2015 13:10:21 +0300	[thread overview]
Message-ID: <CA+t6X7cPuukuRSW8g3a8m_XR6ACkAaik8ZvyUg2JHYFzb++vcA@mail.gmail.com> (raw)
In-Reply-To: <201505160955.47041.michaelkintzios@gmail.com>

2015-05-16 11:55 GMT+03:00 Mick <michaelkintzios@gmail.com>:
> On Saturday 16 May 2015 09:26:14 gevisz wrote:
>> 2015-05-16 10:51 GMT+03:00 gevisz <gevisz@gmail.com>:
>
>> >        So, if I get no better suggestions, I will enable abi_x86_32
>> >        globally and try to update the world once more.
>>
>> Lukily, this approach worked out. Currently I am updating and recompiling
>> 199 packages but the blockers disappeared.
>>
>> >        If that will not work, I will remove the libav USE flag from
>> >        /etc/portage/make.conf and try to update the world for the last
>> >        time.
>>
>> Now, when everything ended well, I can accept that by the phrase
>> "to update the world for the last time" above I meant that I was going
>> to switch to other Linux distribution if this issue with
>> ffmpeg-libav-multilib could not be solved in an elegant way, that is,
>> without poking with every single package, which is really ugly.
>>
>> Luckily, everything ended well and I am happy to stay with Gentoo,
>> but I should mention that, having such issues with multilib profile,
>> enabling abi_x86_32 on per package base really should be unrecommended
>> way to maintain the system and users should be warned about it.
>
> I'm afraid I cannot agree with you on this.  On older PCs I would rather did
> not have to install abi_x86_32 for packages that I don't need to.  The
> granular approach suits me better and also aligns better with the light-footed
> Gentoo approach.

With this "light-footed approach" I had about two full-screen rubbish
in my /etc/portage/make.conf file and kept adding on almost every update.

> I think had you followed my suggestion you could have found that
> by remerging half a dozen packages at most, your conflict would
> have been resolved.

I think so, but this is what I call ugly.

> Either way you got a result, so whatever works.  :-)

Yes, thank you.


  reply	other threads:[~2015-05-16 10:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  5:18 [gentoo-user] libav and ffmpeg on the same computer issue once again gevisz
2015-05-15  5:45 ` Gregory Woodbury
2015-05-15  6:04   ` Gevisz
2015-05-15 17:30     ` Alexander Kapshuk
2015-05-15 18:51       ` Mick
2015-05-16  5:52       ` gevisz
2015-05-16  6:44         ` Alan McKinnon
2015-05-16  7:51           ` gevisz
2015-05-16  8:26             ` gevisz
2015-05-16  8:55               ` Mick
2015-05-16 10:10                 ` gevisz [this message]
2015-05-16 10:19                   ` gevisz
2015-05-16 10:20                   ` Neil Bothwick
2015-05-16 10:40                     ` gevisz
2015-05-16 10:52                       ` Mick
2015-05-16 11:04                         ` Neil Bothwick
2015-05-16 11:16                     ` Rich Freeman
2015-05-16 11:50                       ` Neil Bothwick
2015-05-16 12:57                         ` Rich Freeman
2015-05-17 14:45                           ` Neil Bothwick
2015-05-16 10:33                   ` Mick
2015-05-16 10:43                     ` gevisz
2015-05-16 12:53               ` gevisz
2015-05-16 14:12                 ` Rich Freeman
2015-05-16 15:57                   ` gevisz
2015-05-16 12:50             ` Alan McKinnon
2015-05-16 13:02               ` gevisz

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=CA+t6X7cPuukuRSW8g3a8m_XR6ACkAaik8ZvyUg2JHYFzb++vcA@mail.gmail.com \
    --to=gevisz@gmail.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