Opened 17 years ago

Last modified 7 months ago

#5001 new enhancement

RFE: 'port upgrade' could report # of packages to be upgraded

Reported by: mguthaus@… Owned by: macports-tickets@…
Priority: Normal Milestone: MacPorts Future
Component: base Version:
Keywords: Cc: unknown@…, cooljeanius (Eric Gallager), jan.matousek@…, raimue (Rainer Müller), gguthe@…, ryandesign (Ryan Schmidt), mkae (Marko Käning)
Port:

Description (last modified by mf2k (Frank Schima))

This is a pretty simple user-interface suggestion. As I sit here waiting for DP to finishing upgrading, I have no idea how man packages are left. Windows, OSX, etc always have "progress bars", but these are typically in units of time and so could not be implemented in DP. However, a status of the number of packages would be VERY useful. For example,

--->  Cleaning libgnomecanvas
--->  Finished package 27 of 47
--->  Fetching libgnome

Perhaps, even at the beginning of doing an upgrade, give a message:

"47 packages to be upgraded. Continue (Y/N)?"

I can get the information of which packages are going to be updated with "port outdated", so this is just a matter of displaying the information.

Thanks,

Matt

Change History (13)

comment:1 Changed 17 years ago by mguthaus@…

Another addition... at the end you can add:

Sucessfully upgraded 42 packages. 5 had errors.

comment:2 Changed 17 years ago by unknown@…

Cc: unknown@… added

comment:3 Changed 16 years ago by markd@…

Summary: upgrade status informationRFE: 'port upgrade' could report # of packages to be upgraded

comment:4 Changed 16 years ago by pipping@…

Milestone: MacPorts 1.5

comment:5 Changed 15 years ago by nox@…

Priority: ExpectedNormal
Version: 1.0

comment:6 Changed 15 years ago by jmpp@…

Description: modified (diff)
Milestone: MacPorts 1.5MacPorts base enhancements

comment:7 Changed 12 years ago by mf2k (Frank Schima)

Description: modified (diff)

comment:8 Changed 10 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:9 Changed 10 years ago by ryandesign (Ryan Schmidt)

Cc: jan.matousek@… raimue@… gguthe@… ryandesign@… added

Has duplicate #15167. #15939 is not a duplicate but is a related idea.

I don't think we want to burden MacPorts with interactive prompting like "Continue (Y/N)?".

comment:10 Changed 10 years ago by jmroot (Joshua Root)

port(1) is intentionally non-interactive, but MacPorts doesn't have to provide only one interface.

comment:11 Changed 9 years ago by mkae (Marko Käning)

Cc: mk@… added

I don't need interactivity...

...but If I install a lot of ports (e.g. when I am setting up a machine from scratch) or upgrade an installation which hadn’t been upgraded for a longer time I am overwhelmed by the amount of lines flooding my console…

I would be happier if a few additional lines would be informing me about the progress e.g. like this

--->  Installing 193 ports
--->  (1/193) === Port skrooge ===
--->  Fetching skrooge
--->  Verifying checksum(s) for skrooge
--->  Extracting skrooge
--->  Configuring skrooge
--->  Building Scrooge
--->  Staging skrooge into destroot
--->  Deactivating skrooge-devel @0.8.0-1215845_0
--->  Cleaning skrooge-devel
--->  Computing dependencies for skrooge
--->  Installing skrooge @0.8.0.6_0
--->  Activating skrooge @0.8.0.6_0
--->  Cleaning scrooge
--->  (2/193) === Port blablah ===
--->  Fetching blablah
.
.
.

where of course to be installed dependencies would also count.

Last edited 9 years ago by mkae (Marko Käning) (previous) (diff)

comment:12 Changed 6 years ago by mkae (Marko Käning)

Any update on this one in the light of MacPorts recent overhaul??

comment:13 in reply to:  10 Changed 7 months ago by cooljeanius (Eric Gallager)

Replying to jmroot:

port(1) is intentionally non-interactive, but MacPorts doesn't have to provide only one interface.

Ok this has changed; now MacPorts is interactive... This might be a topic for a separate bug, but on the topic of interactivity, I'm thinking that one thing that could improve it would be to add a default timeout value for all interactive prompts? For Fink it's 60 seconds, IIRC

Note: See TracTickets for help on using tickets.