Opened 20 years ago

Last modified 11 years ago

#2020 new enhancement

port command should let me, optionally, see times — at Initial Version

Reported by: ray@… Owned by: macports-tickets@…
Priority: Normal Milestone: MacPorts Future
Component: base Version:
Keywords: logging Cc:
Port:

Description

I usually do something like:

% date ; port install blender ; date

This does not actually give me what I want.

If it causes the download of 5 things, and it is sitting there on the last one five hours later, I want to know: Did each one take 1 hour, or did the first take 5 seconds each and the last 5 hours?

As it gives you each line below, it should, if I have called it with an option, give me a timestamp:

---> Fetching coreutils ---> Attempting to fetch coreutils-5.2.1.tar.bz2 from ftp://ftp.gnu.org/gnu/coreutils ---> Verifying checksum(s) for coreutils ---> Extracting coreutils ---> Configuring coreutils ---> Building coreutils with target all ---> Staging coreutils into destroot ---> Installing coreutils 5.2.1_1 ---> Activating coreutils 5.2.1_1 ---> Fetching ghostscript

Then it could be:

Wed Jul 7 10:15:49 PDT 2004 ---> Fetching coreutils Wed Jul 7 10:15:49 PDT 2004 ---> Attempting to fetch coreutils-5.2.1.tar.bz2 from ftp://ftp.gnu. org/gnu/coreutils Wed Jul 7 10:15:49 PDT 2004 ---> Verifying checksum(s) for coreutils Wed Jul 7 10:15:49 PDT 2004 ---> Extracting coreutils Wed Jul 7 10:15:49 PDT 2004 ---> Configuring coreutils Wed Jul 7 10:15:49 PDT 2004 ---> Building coreutils with target all Wed Jul 7 10:15:49 PDT 2004 ---> Staging coreutils into destroot Wed Jul 7 10:15:49 PDT 2004 ---> Installing coreutils 5.2.1_1 Wed Jul 7 10:15:49 PDT 2004 ---> Activating coreutils 5.2.1_1 Wed Jul 7 10:15:49 PDT 2004 ---> Fetching ghostscript

Of course, the times would chnage. You know what I mean.

Change History (0)

Note: See TracTickets for help on using tickets.