Re: [gentoo-portage-dev] two remarks on portage-2.0.51-r2

[Roman Gaufman <hackeron@gmail.com>]

1) If you dont know how to echo package-name
>>/etc/portage/package.keywords you shouldnt even bother with masked
or hard masked packages.

2) Emerging path-to-ebuild doesnt append package to the world file,
thus breaking emerge depclean and emerge -up world. --- Very bad idea
and over long term can seriously break system concistency.

To maintain the concistency of your system, allowing you to have a
system as clean as when you installed years after, these 2 things
should be avoided at all cost, and thus deprecated and warned highly
against.


On Sat, 23 Oct 2004 05:17:15 -0700 (PDT), Pablo De Napoli
<pdenapo@yahoo.com> wrote:
> I see that portage-2.0.51-r2 is now stable.
> However, It has some useful features that are deprecated or broken.
> 
> 1) emerge --upgradeonly
> 
> Why is this deprecated? I think it is endeed a useful feature.
> I'm not sure that the files /etc/portage/package* are a good (esay-to-use)
> replacement for it.
> 
> 2) emerge ebuild by path
> 
> Acording to the man page, this is broken, however it is the most obvious way
> to specify an ebuild, isn't it?
> 
> Why is this feature broken, could anybody find out?
> 
> I think is very important to keep the quality of portage to the highest standards, so I
> suggest not to realese as stable a version with important features broken.
> 
> Best regards
> 
> Pablo De Napoli
> 
> 
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
> 
> --
> gentoo-portage-dev@gentoo.org mailing list
> 
>

--
gentoo-portage-dev@gentoo.org mailing list