From: "Arttu V." <arttuv69@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: package.keywords
Date: Mon, 22 Jun 2009 18:14:55 +0300 [thread overview]
Message-ID: <fecdbac60906220814i601f6dffk5f8e7e439926b595@mail.gmail.com> (raw)
In-Reply-To: <loom.20090622T141046-284@post.gmane.org>
On 6/22/09, James <wireless@tampabay.rr.com> wrote:
> Where do I read more and find more of the latest example for
> syntax with portage and the different files therein?
<snip />
> It should have read:
>
> 'man portage' does not show the use of the (><=) syntax
> within the package.keywords file ?
No, but it instructs one to peek into man 5 ebuild for the info. If
you look again at the portage manpage, the section on package.keywords
states of the file format:
"one DEPEND atom per line followed by additional KEYWORDS"
And at the top (Glossary) it says about these atoms:
"DEPEND atom
A string which matches a package. It is of the
form category/package. It may also contain optional logical operators
and versions.
More reading: ebuild(5)"
Follow this "more reading"-hint by entering "man 5 ebuild". The
resulting manpage tells you quite extensively (even everything?) about
the atoms, with many examples, and more.
It takes a meticulous, technically inclined (or otherwise
anal-retentive? :) ) mind to read these manpage-thingies which were
structured and invented before the modern hypertext-intarweb hit the
streets two decades ago. And sure, some of them are written badly, but
IMHO the gentoo ones are pretty ok from a user's POV.
So, as a conclusion, you probably want to use ~ instead of >= in there
as you apparently are running a mostly stable box (arch) instead of
testing (~arch)?
--
Arttu V.
next prev parent reply other threads:[~2009-06-22 15:14 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. [this message]
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.
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=fecdbac60906220814i601f6dffk5f8e7e439926b595@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