GeezerVison is showing github.com — Print install and remove messages below transaction summary by Duncaen · Pull Request #572 · void-linux/xbps
Conversation
Continuation of #421.
-n does not print the messages at the moment, I don't think breaking the parseable output is a good idea.
- removed the callbacks for the message, since its a lot easier to just print and work with the messages from where the transaction is summarized.
- removed
xbps_cb_messge since its pointless, we can just print the data directly.
- simplified the message formatting (removed the big = padding, I think it looks better without, but this is arguable).
[*] Updating repository `https://repo-de.voidlinux.org/current/x86_64-repodata' ...
[*] Updating repository `https://repo-de.voidlinux.org/current/debug/x86_64-repodata' ...
[*] Updating repository `https://repo-de.voidlinux.org/current/nonfree/x86_64-repodata' ...
[*] Updating repository `https://repo-de.voidlinux.org/current/multilib/x86_64-repodata' ...
[*] Updating repository `https://repo-de.voidlinux.org/current/multilib/nonfree/x86_64-repodata' ...
Name Action Version New version Download size
SDL_gfx install - 2.0.26_2 42KB
OpenXcom install - 1.0_5 1622KB
GraphicsMagick install - 1.3.40_1 85KB
Size to download: 1750KB
Size required on disk: 5247KB
Space available on disk: 810GB
[*] OpenXcom install message:
OpenXcom requires a vanilla version of the original
UFO: Enemy Unknown/X-COM: UFO Defense (any edition).
See /usr/share/doc/openxcom/README.txt for details.
[*] GraphicsMagick install message:
The libgraphicsmagick-devel package contains the GraphicsMagick PERL
extension. To install this extension follow the instructions in:
/usr/share/doc/GraphicsMagick/PerlMagick/README.txt
Do you want to continue? [Y/n]
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
icp1994 reacted with thumbs up emoji
dmarto reacted with heart emoji
All reactions
-
👍
1 reaction
-
❤️
1 reaction
-n does not print the messages at the moment, I don't think breaking the parseable output is a good idea.
I like the idea of putting them on stderr, that should prevent breaking anything that doesn't 2>&1 as discussed on irc, a regular run can be done and no can be chosen if users want to see these messages, as dryrun is probably only used for update checking scripts
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-n is only mode that shows transaction without root, sometimes I use it for quick look how it would look like. Yet, can't see any good way to include messages there.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Reviewers
1 more reviewer
Reviewers whose approvals may not affect merge requirements
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|