On Thu, 14 Feb 2008 11:46:10 -0500
"Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> How hard would it be to add the following to portupgrade-devel:
>
> 1. Progress report for -a builds (i.e. after and/or at the start of a
> port build it says
On Fri, Feb 15, 2008 at 11:30:17AM + I heard the voice of
Alex Zbyslaw, and lo! it spake thus:
> Matthew D. Fuller wrote:
>
>> And it
>> doesn't tell me anything unless I happen to be watching the terminal
>> at just the right time, and read quick before it scrolls off. I have
>> to wait 'til
Matthew D. Fuller wrote:
And it
doesn't tell me anything unless I happen to be watching the terminal
at just the right time, and read quick before it scrolls off. I have
to wait 'till the end for any details that.
portupgrade {your stuff} |& tee /tmp/portupgrade.log # [1]
Now you can jus
On Thu, Feb 14, 2008 at 01:46:08PM -0800 I heard the voice of
Doug Barton, and lo! it spake thus:
>
> ... and I repeat my thesis that what you're really interested in is
> how much time is left, not how many ports are left to build, and no
> tool is going to be able to tell you that.
No, but a to
Quoting "Aryeh M. Friedman" <[EMAIL PROTECTED]> (from Thu, 14
Feb 2008 11:46:10 -0500):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How hard would it be to add the following to portupgrade-devel:
1. Progress report for -a builds (i.e. after and/or at the start of a
port build it says how m
Doug Barton worte:
I'm going to respond to these from the portmaster perspective to try
and give some additional context. No criticism of portupgrade is
intended, since I've said many times that they are not completely
overlapping in feature sets.
Doug, I feel no resentment on criticism of port
Doug Barton wrote:
Aryeh M. Friedman wrote:
Doug Barton wrote:
The idea is more along the lines of knowing how far you are away from
completing the whole build
... and I repeat my thesis that what you're really interested in is
how much time is left, not how many ports are left to build,
On Thu, 14 Feb 2008 11:46:10 -0500
"Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote:
> 2. Interruptible -a builds (i.e. portupgrade -af will restart from
> where it was last interrupted [perhaps with an additional flag?])
>
FWIW you can already achieve the same end using the features of
pkg_glob
e
Aryeh M. Friedman wrote:
> Doug Barton wrote:
> The idea is more along the lines of knowing how far you are away from
> completing the whole build
... and I repeat my thesis that what you're really interested in is
how much time is left, not how many ports are left to build, and no
tool is going
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
|
| | Portmaster has this feature, you add the -R flag along with -f (or
| | -r). (Note, not all command line options mean the same thing for both
| | tools. Look at the man pages.) You can also use the -C flag to avoid
| | deleting what you've alrea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug Barton wrote:
| I'm going to respond to these from the portmaster perspective to try
| and give some additional context. No criticism of portupgrade is
| intended, since I've said many times that they are not completely
| overlapping in feature s
I'm going to respond to these from the portmaster perspective to try
and give some additional context. No criticism of portupgrade is
intended, since I've said many times that they are not completely
overlapping in feature sets.
I'm also responding since I think these are interesting questions and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How hard would it be to add the following to portupgrade-devel:
1. Progress report for -a builds (i.e. after and/or at the start of a
port build it says how many ports are left to be processed)
2. Interruptible -a builds (i.e. portupgrade -af will
13 matches
Mail list logo
