From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] audacity-2.0.5 failed to compile
Date: Fri, 4 Sep 2015 09:34:35 +0100 [thread overview]
Message-ID: <20150904093435.20e2dc8b@digimed.co.uk> (raw)
In-Reply-To: <55E8AF2F.8050608@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
On Thu, 3 Sep 2015 22:35:59 +0200, Alan McKinnon wrote:
> Cleanups: Sometimes when cleaning up you'll delete something you really
> do need, and you forget why you put it in world. Maybe emerge world puts
> it back, but more likely stuff just breaks. Keep a list of all removals
> so if you find breakage you can add things back. The classic case is
> libs you need for your own code - you probably don't have an ebuild for
> that and therefore no deps for portage to use.
> Sets: You have a many-purpose machine so you might find sets useful,
> mostly because you can't add comments to world. You can with sets. They
> are just files in /etc/portage/sets/ that list packages. You add them to
> the system with emerge @<set_name>. Here is one of mine:
I combine these two ideas and have a set called dependencies that
contains a commented list of packages that are needed by non-portage
software. Then I just emerge -n @dependencies.
The -n flag is useful when cleaning world, it adds the package to world
without re-emerging it unnecessarily.
--
Neil Bothwick
Tact is for people who don't understand sarcasm.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-09-04 8:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 22:04 [gentoo-user] audacity-2.0.5 failed to compile thelma
2015-09-01 22:55 ` Fernando Rodriguez
2015-09-01 23:05 ` thelma
2015-09-02 1:22 ` Alec Ten Harmsel
2015-09-02 2:23 ` Fernando Rodriguez
2015-09-02 2:57 ` wraeth
2015-09-02 4:24 ` thelma
2015-09-02 4:57 ` wraeth
2015-09-02 5:59 ` Mick
2015-09-02 11:50 ` Alan McKinnon
2015-09-02 12:04 ` Dale
2015-09-02 20:25 ` thelma
2015-09-03 13:06 ` Alec Ten Harmsel
2015-09-03 13:19 ` Alan McKinnon
2015-09-03 13:56 ` thelma
2015-09-03 14:27 ` Alan McKinnon
2015-09-03 17:22 ` Alec Ten Harmsel
2015-09-03 20:10 ` Alan McKinnon
2015-09-03 18:57 ` Fernando Rodriguez
2015-09-03 19:11 ` thelma
2015-09-03 19:30 ` Mick
2015-09-03 19:41 ` thelma
2015-09-03 20:35 ` Alan McKinnon
2015-09-04 8:34 ` Neil Bothwick [this message]
2015-09-03 19:24 ` Mick
2015-09-03 19:56 ` thelma
2015-09-03 20:41 ` Alan McKinnon
2015-09-04 8:38 ` Neil Bothwick
2015-09-04 13:24 ` Alan McKinnon
2015-09-04 21:31 ` Neil Bothwick
2015-09-04 9:42 ` Peter Humphrey
2015-09-04 10:00 ` Mick
2015-09-04 10:19 ` Peter Humphrey
2015-09-04 10:31 ` Neil Bothwick
2015-09-04 10:48 ` Peter Humphrey
2015-09-04 13:26 ` Alan McKinnon
2015-09-03 14:28 ` Neil Bothwick
2015-09-03 15:26 ` thelma
2015-09-03 15:31 ` Alan McKinnon
2015-09-03 15:33 ` thelma
2015-09-03 16:16 ` Alexander Kapshuk
2015-09-03 17:22 ` Neil Bothwick
2015-09-03 20:44 ` Dale
2015-09-02 13:28 ` [gentoo-user] " James
2015-09-02 5:55 ` [gentoo-user] " Fernando Rodriguez
2015-09-02 9:15 ` Gevisz
2015-09-02 9:50 ` wraeth
2015-09-02 18:52 ` Andreas K. Huettel
2015-09-02 20:31 ` Alan McKinnon
2015-09-03 12:47 ` Alec Ten Harmsel
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=20150904093435.20e2dc8b@digimed.co.uk \
--to=neil@digimed.co.uk \
--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