I believe that the program "time" (sys-apps/time-1.7-r1) should be added to the
base system. It is a useful utility, and several things rely upon it (such as
my script above! Yes yes, I know, shameless plug...). It includes greater
functionality than the bash `time` builtin, including the ability to change its
output, and redirect it elsewhere, things that cannot be done with bash's
Please seriously consider my request, it is a very useful program, and one I
think ought to be installed by default.
what does the included script do ?
also, it probably wont be accepted (whatever it is ;]) due to the fact you make
use of /log/ ... maybe if you made use of /tmp/log/ or /var/log/failed/ it
would go smoother
The script included in the URL for this bugreport is mentioned in bug #4634:
and was included merely for example, I will take note of your suggestions, but
they don't quite apply here, this report was simply to get the "time" command
included in the base system, preferabbly before release 1.4.
Don't know whether we should do this or not, assigning back to bug-wranglers
Release gang, what do y'all think?
Hmmm good question, I'm not sure it's really essential to the base system...it
doesn't really provide a needed function to base. Anyone that wants it can
easily emerge it anywhere in the process as it has no DEPS aside from glibc...
I am of the mind to keep the base system trimmed down to what is really
absolutely necessary, and while this is not a big util it is a step in the
worng direction for sticking with essentials.
Any other comments?
I would tend to agree with that, myself, to be honest. Gentoo is
characteristically about non-bloat. I do not know what your script does, but if
you're ebuilding it, make it RDEPEND on sys-apps/time, and you're set.
There are many nice ideas, what can be added to stages. If we fullfill each
wish, stage1 will soon fill a whole cd ];-) ...
My suggestion: As less bloat as possible and when our new split of the build
process into stage0 and stage1 has produced a fine 1.4_final, have a look at the
build process stage0-to-1. It will turn out that stage0 can be seen as stage1
constriction kit. with a bit of doc and some few(!) extensions everyone can
roll his own stage1 then. this would be able to satisfy wishes like for example
fte as default editor in stage1 or other neat things...
I dont think we shourd fullfill each wish directly but show the way to get it
and have a look at not unneededly blockung customizations. It is providing some
things in a standardized (prebuilt stages2+3 with -O3 as optimazation only) but
enable the user to reach his goal on his on, maybe supported by some tools from
Try the output configurability of the 'date' util.
My official standing: I want the base as lean as possible, and just my
USE flags should pull in what *I* want. I want full control, so everything
should be functional, but simple.
assigned/fixed borks the database,changing to resolved:fixed.