From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
Date: Sat, 16 May 2015 11:52:48 +0100 [thread overview]
Message-ID: <201505161152.49755.michaelkintzios@gmail.com> (raw)
In-Reply-To: <CA+t6X7fZ38XyPiZcqAMM5yTQhqNX4330Bcq0X2-nWKoXQkgstA@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1370 bytes --]
On Saturday 16 May 2015 11:40:01 gevisz wrote:
> 2015-05-16 13:20 GMT+03:00 Neil Bothwick <neil@digimed.co.uk>:
> > As Mick says, you get to choose, but the per-package approach is
> > definitely lighter on the system. Enabling it globally may be less work
> > though. I say "may" because when I tried that it introduced some
> > breakages,
>
> If enabling abi_x86_32 globally may introduce breakages, then
> the multilib profile is even more broken than I ever thought. :-(
>
> > so I went for the per-package approach.
> > --
> > Neil Bothwick
> >
> > Things are more like they are today than they ever have been before.
>
> Yes, I do remember installing Linux on a brand-new laptop in 2003.
>
> I had to compile a new kernel only to get the command prompt.
>
> And, to get a graphic interface, I had to wait for a new release
> of the distribution in 2004. :(
Oh the nostalgia of the good old days! Back then we had to (bootstrap)^2 to
begin the installation. I seem to recall 2004.1 as a relatively straight
forward installation vintage/profile, although there were the odd horror
stories depending on hardware combos and missing drivers.
PS. I'm waiting for Neil's uncanny signature which if it works correctly it
should come with something like: "Nostalgia, it's not what it used to be"
LOL!
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-16 10:53 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
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 [this message]
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=201505161152.49755.michaelkintzios@gmail.com \
--to=michaelkintzios@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