On Thu, 24 Jan 2013 03:17:06 -0600, Dale wrote: > What Bruce was saying is this. When you use --ask, you can look at the > output of what packages are going to be emerged, what USE flags are > enabled/disabled/changed and other information that could make a person > change a setting all before anything is done. If emerge is doing to > much, to little or some other unwanted thing, you can change it.
I understand that, but it is not relevant to my point. Using -N includes packages that do not need emerging. Either you let them emerge or you filter them out manually, either way is inefficient. Particularly the manual filtering as they will show up again on the next run. Bruce also posted a chained alias he uses, so having to interrupt the process top manually select packages means running the rest of the commands manually too. Like Alan says, trust portage to know your system, let it make the first decision before you review it with --ask. The option is there, I find it useful. I really don't care who else uses itWhat Bruce was saying is this. When you use --ask, you can look at the output of what packages are going to be emerged, what USE flags are enabled/disabled/changed and other information that could make a person change a setting all before anything is done. If emerge is doing to much, to little or some other unwanted thing, you can change it. , but I thought I'd mention it in came anyone still using its shotgun predecessor found the information useful. I am not trying to persuade anyone else to use it and you won't persuade me to stop using it, neither is the point of the post. It's just occurred to me as I was about to hit Send. If you respond to emerge --ask with n, it still returns success, so using that in the middle of a chin of commands is not much help unless you use Ctrl-C instead of n. -- Neil Bothwick I doubt therefore I might be.
signature.asc
Description: PGP signature
