El Jueves, 13 de Septiembre de 2007 21:35, Jeremy Huntwork escribió: > As a complete aside, Manuel, I've gotten to the point of actually hating > the progress bar, I believe. No offense meant. It's a good attempt and I > can appreciate both why you wrote it and why it's written as it is. But > in my experience it slows down the build times, especially on older > hardware, and it doesn't really tell you much of anything. On all my > builds I always truncate common/progress_bar.sh before starting. I know > I mentioned attempting a C-based progress bar at some point, but I > haven't gotten around to it yet. Would anyone care if we made this bit > of code optional in the configuration?
I don't care, I just hate to have a console doing something but outputing nothing for a very long time, like when building GCC with testsite enabled. Thus, if making the progress bar optional, maybe the full make output should be optional (or redirected to a log file) to allow users to do a " cd $JHALFSDIR && make &". -- Manuel Canales Esparcia Usuario de LFS nº2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
