| 1 |
1) If you dont know how to echo package-name |
| 2 |
>>/etc/portage/package.keywords you shouldnt even bother with masked |
| 3 |
or hard masked packages. |
| 4 |
|
| 5 |
2) Emerging path-to-ebuild doesnt append package to the world file, |
| 6 |
thus breaking emerge depclean and emerge -up world. --- Very bad idea |
| 7 |
and over long term can seriously break system concistency. |
| 8 |
|
| 9 |
To maintain the concistency of your system, allowing you to have a |
| 10 |
system as clean as when you installed years after, these 2 things |
| 11 |
should be avoided at all cost, and thus deprecated and warned highly |
| 12 |
against. |
| 13 |
|
| 14 |
|
| 15 |
On Sat, 23 Oct 2004 05:17:15 -0700 (PDT), Pablo De Napoli |
| 16 |
<pdenapo@×××××.com> wrote: |
| 17 |
> I see that portage-2.0.51-r2 is now stable. |
| 18 |
> However, It has some useful features that are deprecated or broken. |
| 19 |
> |
| 20 |
> 1) emerge --upgradeonly |
| 21 |
> |
| 22 |
> Why is this deprecated? I think it is endeed a useful feature. |
| 23 |
> I'm not sure that the files /etc/portage/package* are a good (esay-to-use) |
| 24 |
> replacement for it. |
| 25 |
> |
| 26 |
> 2) emerge ebuild by path |
| 27 |
> |
| 28 |
> Acording to the man page, this is broken, however it is the most obvious way |
| 29 |
> to specify an ebuild, isn't it? |
| 30 |
> |
| 31 |
> Why is this feature broken, could anybody find out? |
| 32 |
> |
| 33 |
> I think is very important to keep the quality of portage to the highest standards, so I |
| 34 |
> suggest not to realese as stable a version with important features broken. |
| 35 |
> |
| 36 |
> Best regards |
| 37 |
> |
| 38 |
> Pablo De Napoli |
| 39 |
> |
| 40 |
> |
| 41 |
> _______________________________ |
| 42 |
> Do you Yahoo!? |
| 43 |
> Declare Yourself - Register online to vote today! |
| 44 |
> http://vote.yahoo.com |
| 45 |
> |
| 46 |
> -- |
| 47 |
> gentoo-portage-dev@g.o mailing list |
| 48 |
> |
| 49 |
> |
| 50 |
|
| 51 |
-- |
| 52 |
gentoo-portage-dev@g.o mailing list |
Archives