On Sun, 2002-02-10 at 06:41, Ilian Zarov wrote:
> 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.

No, 4.2a was latest version at that time (not sure about
currently).

> > Many thanks,
> > 
> > Matt
>  
> 
> 	Best Regards,
> 		Ilian Zarov
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop Team Developer
Cape Town, South Africa