[pacman-dev] [PATCH] Highlight new dependencies brought in by an upgrade

[Connor Behan]

On 15/07/13 09:01 PM, Allan McRae wrote:
> On 16/07/13 13:59, Allan McRae wrote:
>> On 16/07/13 13:41, Connor Behan wrote:
>>> Users trying to keep a lightweight system often scan the list of targets
>>> for red flags. This just makes it easier for them.
>>>
>>> Signed-off-by: Connor Behan <connor.behan at gmail.com>
>>> ---
>> This makes little sense to me.  As a user I would not make the
>> connection that highlighted packages are new dependencies.  In fact, I
>> would expect those to be the targets that are being updated if anything.
>>
>> And we already have VerbosePkgLists for people who want to monitor every
>> detail of the update.
> In addition.   "pacman -Syu foo"  updates and installs foo.   Think
> about what the highlighting does then.
>
It would highlight foo as well as any dependencies of it that weren't
already installed. We could try to be smart about this and only
highlight packages unrelated to what was specified on the command line
but I thought this accomplished the main task without adding any
computation. I also wanted relatively few packages to be highlighted -
the set of packages being updated would be almost every package.

But now that you suggest VerbosePkgLists, the patch doesn't seem so
important. Cheers.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/pacman-dev/attachments/20130715/a8588426/attachment.asc>