On 7/11/06, David Corbin <[EMAIL PROTECTED]> wrote:
I'd like to see an option where certain packages are not upgrade just because
they're out of date, but require an additional command line argument.
Additionally, a tool that I could run that tells me "the following packages
are being 'held back' because a more involved upgrade" - ideally, it would
also provide information on what the required steps are.
I'm I crazy?
I don't think so. Your comments are very much in line with
mine...trying to make the more involved upgrades less error prone.
The one concern I have with taking this out of the standard update
process is that we really need to keep up with the currently 'stable'
software as a minimum. Updating some things that are "simple", but
letting other packages fall behind, is just asking for breakage at
some point. Some recent postings to -dev regarding current software
not building with old gcc versions really point out this fact...
So I don't think we need yet another tool here. I would prefer to see
our existing tools enhanced with this goal in mind.
-Richard
--
[email protected] mailing list
