From: Rich Freeman <rich0@gentoo.org>
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 08:57:15 -0400 [thread overview]
Message-ID: <CAGfcS_nwySm46Zahmz-8bHaM7jvcf6rSwHyTB8UkJiDQ90P+Jg@mail.gmail.com> (raw)
In-Reply-To: <20150516125034.1bc6ee0c@digimed.co.uk>
On Sat, May 16, 2015 at 7:50 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Sat, 16 May 2015 07:16:58 -0400, Rich Freeman wrote:
>>
>> Well, it can be a lot more than two screens of text. I have 1300
>> lines of package.use, almost all of it for abi_x86_32. I suspect that
>> this the result of stuff like steam, wine, android-sdk-update-manager,
>> and eternal-lands - all packages that involve graphics libraries and
>> toolkits with huge dependency trees.
>
> Does that include the several lines of comments, often repeated, that
> portage includes in the auto-unmask output? I just checked two systems
> for abi_x86_32 and got around 130 lines in one and 220 in the other.
Yes, it does. The number of actual configuration lines is much
smaller of course - probably 1/5th of the total.
My point wasn't so much that this was an inordinate number of 32-bit
packages, given my list of installed packages. It was more about the
fact that on a system that I'm trying to keep fairly minimal other
than my explicit preferences I end up with a huge config file that
tends to mix my preferences with a lot of stuff that exists solely to
satisfy the depgraph. It would be like sticking every package I
install in my world set.
There are some ways around this which I'll probably get around to on a
rainy day:
1. Take better advantage of the fact that package.use can be a
directory and have several files. The 32-bit flags would go in their
own file. Autounmask goes in a separate file with a z at the start of
the name and the intent is that lines in this file get moved to the
appropriate files. Then from time to time the 32-bit flags can be
deleted and re-created to keep them minimal as installed packages
change.
2. What I'd really like to get to is a point where all my systems are
defined by ansible configs or the like. I've already started
container-izing many of my services to cut down on interactions - this
way when I do random package updates I'm not dealing with mysql
breaking or apache or whatever. However, this increases the amount of
updating I have to do, and I'd like to bring that back down using a
tool like ansible.
--
Rich
next prev parent reply other threads:[~2015-05-16 12:57 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
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 [this message]
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=CAGfcS_nwySm46Zahmz-8bHaM7jvcf6rSwHyTB8UkJiDQ90P+Jg@mail.gmail.com \
--to=rich0@gentoo.org \
--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