| 1 |
On 7/11/06, David Corbin <gentoo.org@××××××××××.com> wrote: |
| 2 |
> I'd like to see an option where certain packages are not upgrade just because |
| 3 |
> they're out of date, but require an additional command line argument. |
| 4 |
> Additionally, a tool that I could run that tells me "the following packages |
| 5 |
> are being 'held back' because a more involved upgrade" - ideally, it would |
| 6 |
> also provide information on what the required steps are. |
| 7 |
> |
| 8 |
> I'm I crazy? |
| 9 |
|
| 10 |
I don't think so. Your comments are very much in line with |
| 11 |
mine...trying to make the more involved upgrades less error prone. |
| 12 |
|
| 13 |
The one concern I have with taking this out of the standard update |
| 14 |
process is that we really need to keep up with the currently 'stable' |
| 15 |
software as a minimum. Updating some things that are "simple", but |
| 16 |
letting other packages fall behind, is just asking for breakage at |
| 17 |
some point. Some recent postings to -dev regarding current software |
| 18 |
not building with old gcc versions really point out this fact... |
| 19 |
|
| 20 |
So I don't think we need yet another tool here. I would prefer to see |
| 21 |
our existing tools enhanced with this goal in mind. |
| 22 |
|
| 23 |
-Richard |
| 24 |
-- |
| 25 |
gentoo-user@g.o mailing list |
Archives