On 10/21/2011 03:29 AM, Dieter Plaetinck wrote:
On Fri, 21 Oct 2011 00:30:12 -0300
Gerardo Exequiel Pozzi<[email protected]> wrote:
On 10/14/2011 10:56 PM, Gerardo Exequiel Pozzi wrote:
On 10/14/2011 02:20 PM, Gerardo Exequiel Pozzi wrote:
On 10/13/2011 05:44 PM, Dieter Plaetinck wrote:
Hello senior Gerardo,
how about making a build.sh command argument to disable progress
bars? I.e. it would call mksquashfs -no-progress
my logfiles would look prettier :)
I thought maybe you could do "don't show progress bars when
non-verbose" but I like the verbose flag so I can see
errors/warnings. or maybe you should always show errors/warnings,
also when not verbose. then I could run without the verbose flag
and don't see any progress bars.
Dieter
OK. I will look at the code again in few days. I am a bit busy in
these weeks.
OK just disabled progress bar, if you need other thing, please let
me know.
Error handling is a bit special (bash -x), it stop at the first
thing that goes bad. Maybe can be a good idea to trap this and show
an error message that says "for details enable verbose mode".
http://projects.archlinux.org/archiso.git/commit/?id=51db47e74bb5209bb242d99e6d69b1f683dd3085
Maybe you can also want to disable progress bars during package
download when making "core-repo" for core isos.
right?
yes, I would like all progress bars gone when running archiso from my scripts.
at the same time, i realise when running archiso interactively, progress bars
are useful.
Dieter
I prefer to not add more complexity, in other words I will disable
progress bars, keeping things like when wget was used (if I do not
remember bad).
--
Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1
