From: Ilian Zarov <coder@descom.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] help with readline confusion
Date: 10 Feb 2002 06:41:45 +0200 [thread overview]
Message-ID: <1013316107.28406.42.camel@gentoo.labs.darklight.sh> (raw)
In-Reply-To: <1013248371.17757.14.camel@gentoo.shacknet.nu>
On Sat, 2002-02-09 at 11:52, Matthew Kennedy wrote:
> My question has two parts. 1.I had expected that the "latest version
> available" would show 4.2a, but it doesn't. I must be missing something
> about how emerge determines which ebuild is the latest available. Is
> 4.2a not to be used just right now?
emerge checks if the packages is blocked (whether it is included in
/usr/portage/profiles/package.mask). Blocked packages are usually
broken/incomplete ebuilds or early alpha/beta versions of the specified
application.
> 2. octave want's 4.2. I can satisfy it with an "ebuild
> readline-4.2a.ebuild merge", but then I don't think i should, because if
> users aren't getting 4.2 from an emerge, then I doubt I can expect them
> to ebuild it manually when they emerge the octave package. Does this
> logic sound right?
You should talk to an @gentoo.org developer about removing readline-4.2a
from package.mask if you consider it stable enough (isn't this actually
an alpha version ?). Not very sure of how the package.mask stuff is
handled.
> Many thanks,
>
> Matt
Best Regards,
Ilian Zarov
next prev parent reply other threads:[~2002-02-10 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 9:52 [gentoo-dev] help with readline confusion Matthew Kennedy
2002-02-10 4:41 ` Ilian Zarov [this message]
2002-02-17 4:39 ` Martin Schlemmer
2002-02-17 4:35 ` Martin Schlemmer
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=1013316107.28406.42.camel@gentoo.labs.darklight.sh \
--to=coder@descom.com \
--cc=gentoo-dev@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