From: "Arttu V." <arttuv69@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: package.keywords
Date: Tue, 23 Jun 2009 13:51:12 +0300 [thread overview]
Message-ID: <fecdbac60906230351j388e9b18y273f6f3bfba7d020@mail.gmail.com> (raw)
In-Reply-To: <loom.20090622T154452-892@post.gmane.org>
On 6/22/09, James <wireless@tampabay.rr.com> wrote:
> Arttu V. <arttuv69 <at> gmail.com> writes:
>
>> More reading: ebuild(5)"
>
> Ah, ok so there is not restriction on using any of the
> the boolean operators in any config file underneath
> /etc/portage? as section 5 does not mention any....
Well, for those files that are actually supposed to contain DEPEND
atoms that is probably true. I haven't checked the whole man page and
all files it lists to see if it places any restrictions on some
specific files therein, so I'm a bit timid to claim full "no limits"
either. But for package.keywords it didn't mention any limits and I'd
believe the others don't have them either. :)
Still, the best identifier of the allowed syntax is probably portage
itself. Make a typo in files under /etc/portage and portage will tell
you next time you emerge -pv something or emerge -av something.
And it also breaks in a quite predictable fashion when it reads your
typos in those files: it will just drop the lines it doesn't
understand (while also printing warning messages) and then dutifully
proceed to next line. So if ever in doubt, you can try it and see what
portage's parser thinks about your "fuzz-test". :)
> This is my (mis)conception, although, as you have suggest,
> there are (gentoo) cultural norms that do suggest
> certain boolean operations should not be used,
> in say for example, package.keywords?
Not sure if by cultural norms you're referring to something I'd rather
label as "best practices"? :)
But then again, there are best practices for bleeding edge folks and
best practices for "stability is paramount" folks and they may
overlap, but most likely they aren't quite the same.
> I'm mostly running stable with exceptions being enabled
> via the /etc/portage file structure. Usually it's small,
> but now with kde4, BLOAT is my modus operandi,
> not by choice......
Then, again, you probably don't want the >= as it will unmask the
latest testing version currently available, plus in future any new
testing grade versions as they get added to portage tree. What you
want is either = or ~. (And do note that ~ at the front of a DEPEND
atom means a different thing from the testing keyword in ~arch).
But it is all up to you to decide, you're the commander'n'chief of
your own boxen.
--
Arttu V.
prev parent reply other threads:[~2009-06-23 10:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 13:58 [gentoo-user] package.keywords James
2009-06-22 14:08 ` Albert Hopkins
2009-06-22 14:18 ` [gentoo-user] package.keywords James
2009-06-22 15:14 ` Arttu V.
2009-06-22 15:51 ` James
2009-06-22 20:28 ` Alan McKinnon
2009-06-23 14:40 ` James
2009-06-23 14:54 ` Nikos Chantziaras
2009-06-23 15:28 ` James
2009-06-23 15:40 ` Nikos Chantziaras
2009-06-23 16:09 ` [gentoo-user] ReSOLVED: package.keywords James
2009-06-23 18:42 ` Alan McKinnon
2009-06-23 14:55 ` [gentoo-user] package.keywords Neil Bothwick
2009-06-23 15:36 ` James
2009-06-23 15:05 ` Alan McKinnon
2009-06-23 15:49 ` James
2009-06-23 18:39 ` Alan McKinnon
2009-06-22 22:17 ` Neil Bothwick
2009-06-22 23:17 ` Dale
2009-06-22 23:45 ` Neil Bothwick
2009-06-23 6:42 ` Alan McKinnon
2009-06-23 6:51 ` Dale
2009-06-23 7:33 ` Neil Bothwick
2009-06-23 7:38 ` Dale
2009-06-23 8:27 ` Alan McKinnon
2009-06-23 9:16 ` Weitao Sun
2009-06-23 9:18 ` Dale
2009-06-23 10:16 ` Neil Bothwick
2009-06-23 10:51 ` Arttu V. [this message]
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=fecdbac60906230351j388e9b18y273f6f3bfba7d020@mail.gmail.com \
--to=arttuv69@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