From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage getting mixed up with USE?
Date: Wed, 22 Jun 2011 17:22:08 +0100 [thread overview]
Message-ID: <20110622172208.5801138e@zaphod.digimed.co.uk> (raw)
In-Reply-To: <15413157.QhsxscBRlY@nazgul>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
On Wed, 22 Jun 2011 17:31:40 +0200, Alan McKinnon wrote:
> > autounmask is set by default, you need to explicitly set it to off.
> is it invisibly on then? I don't have it in make.conf and it's not in
> FEATURES:
Apparently so, as it doesn't show up in emerge --info here either.
> > > I'm a sysadmin, I have an inherent distrust of all things
> > > software and automagic-config-changers are scary things indeed
> > > :-)
> >
> > autounmask doesn't actually do anything, it only tells you what
> > should be added to /etc/portage/package.use. You need to use
> > autounmask-write for that, which doesn't play nicely if package.use
> > is a directory[1]. However, it does respect the --ask flag, making
> > it safe for all but the most paranoid BOFHs (no names Alan) to use.
> >
> > [1] It writes to a file of its choosing in that directory, with no
> > regard to its relevance. I'd prefer it to write to something like
> > packagename.autounmasked or even just packagename as it adds a
> > comment to the file to explain the content.
>
> Hmmmmmmmmmmm, still sounds like something that should be banned. For
> me at least.
Too right, we can't have software telling us what needs to be done to
install it! What will we use Google for now?
--
Neil Bothwick
Everywhere is walking distance if you have the time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-06-22 16:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 8:18 [gentoo-user] portage getting mixed up with USE? Alan McKinnon
2011-06-22 8:49 ` Daniel Pielmeier
2011-06-22 9:15 ` Alan McKinnon
2011-06-22 9:31 ` Daniel Pielmeier
2011-06-22 9:50 ` Alan McKinnon
2011-06-22 9:47 ` Neil Bothwick
2011-06-22 9:53 ` Alan McKinnon
2011-06-22 10:43 ` Neil Bothwick
2011-06-22 11:54 ` Alan McKinnon
2011-06-22 12:22 ` Daniel Pielmeier
2011-06-22 12:41 ` Alan McKinnon
2011-06-22 14:19 ` Mick
2011-06-22 14:44 ` Neil Bothwick
2011-06-22 15:31 ` Alan McKinnon
2011-06-22 16:05 ` Mick
2011-06-22 16:22 ` Neil Bothwick [this message]
2011-06-22 16:30 ` Sebastian Beßler
2011-06-22 16:59 ` Alan McKinnon
2011-06-23 11:31 ` Daniel Pielmeier
2011-06-23 19:40 ` Alan McKinnon
2011-06-22 17:11 ` Sebastian Beßler
2011-06-22 18:22 ` Dale
2011-06-22 19:16 ` Sebastian Beßler
2011-06-22 20:12 ` Alan McKinnon
2011-06-22 22:35 ` Mick
2011-06-22 22:58 ` Neil Bothwick
2011-06-23 1:35 ` Matthew Finkel
2011-06-23 6:59 ` Sebastian Beßler
2011-06-23 19:38 ` Alan McKinnon
2011-06-23 22:06 ` Neil Bothwick
2011-06-23 22:31 ` Alan McKinnon
2011-06-23 22:56 ` Mike Edenfield
2011-06-24 0:05 ` Neil Bothwick
2011-06-24 0:10 ` Neil Bothwick
2011-06-24 8:00 ` Sebastian Beßler
2011-06-23 20:05 ` Yohan Pereira
2011-06-24 8:11 ` Sebastian Beßler
2011-06-22 10:48 ` Daniel Pielmeier
2011-06-22 11:57 ` Alan McKinnon
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=20110622172208.5801138e@zaphod.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