Opened 20 years ago
Last modified 11 years ago
#2020 new enhancement
Add full logging support to MacPorts build oriented runtime actions
Reported by: | ray@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | MacPorts Future |
Component: | base | Version: | |
Keywords: | logging | Cc: | jmpalacios (Juan Manuel Palacios), ecronin (Eric Cronin), cooljeanius (Eric Gallager), gthb (Gunnlaugur Thor Briem) |
Port: |
Description (last modified by jmpalacios (Juan Manuel Palacios))
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 (13)
comment:1 Changed 19 years ago by olegb@…
severity: | normal → enhancement |
---|
comment:2 Changed 19 years ago by blb@…
Sounds like a generalization of bug 507 (noted for tracking purposes).
comment:3 Changed 19 years ago by olegb@…
Resolution: | → duplicate |
---|---|
Status: | new → closed |
* This bug has been marked as a duplicate of 507 *
comment:4 Changed 18 years ago by jmpalacios (Juan Manuel Palacios)
Description: | modified (diff) |
---|
comment:5 Changed 18 years ago by jmpalacios (Juan Manuel Palacios)
Keywords: | logging added |
---|---|
Milestone: | → MacPorts 1.5 |
Priority: | Expected → Important |
Resolution: | duplicate |
severity: | minor → Normal |
Status: | closed → reopened |
Summary: | port command should let me, optionally, see times → Add full logging support to MacPorts build oriented runtime actions |
Reopening this ticket to track the progress of the logging proposal I originally made for GSoC2007, now documented at PortLoggingProposal. Tentatively setting to the 1.5 milestone and marking #507 as a forward dup if this one, since it's of wider scope. Also adapting ticekt summary to reflect the entire scope of the logging proposal.
-jmpp
comment:6 Changed 18 years ago by jmpalacios (Juan Manuel Palacios)
Owner: | changed from macports-tickets@… to macports-dev@… |
---|---|
Status: | reopened → new |
comment:7 Changed 18 years ago by jmpalacios (Juan Manuel Palacios)
Version: | 1.0 → 1.4.3 |
---|
comment:8 Changed 18 years ago by jmpalacios (Juan Manuel Palacios)
Cc: | jmpp@… added |
---|
comment:9 Changed 17 years ago by nox@…
Priority: | Important → High |
---|---|
Version: | 1.4.3 |
comment:10 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)
Milestone: | MacPorts 1.5 → MacPorts base enhancements |
---|---|
Priority: | High → Normal |
comment:11 Changed 17 years ago by ecronin (Eric Cronin)
Cc: | ecronin@… added |
---|
This is a suggested enhancement, not a bug.