Hi,
it's a nice idea to implement something like this, but I guess getting
all details right will be difficult. Especially to correctly notify all
"out of space" conditions.
As a quick conceptual test you could start not worrying about the
real error, but build any failed package a second time without
TMPFS, this might be just a couple of lines of code.
René
Mike N wrote:
Hello,
T2 has the nice TMPFS RAM file system compilation support.
In practice this is a bit difficult feature to be used because certain
packages require soooo much disk space from RAM (firefox, xorg etc).
However, most of the packages are quite small and would fit just fine into
TMPFS.
Is it possible to configure T2 Build-Target script to use TMPFS by default
and
if compilation of a pkg fails in "out of disk space" error then T2 would
revert
back to default disk usage for that package? Next package would becompiled
into TMPFS again and so on.
This would be handy way to speed up compilation in batch build cases where
machine is left to compile over night. It would not matter to compile few
packages "twice". In ideal cases T2 could keep track of these "too big"
packages
in some cache file and not to compile them in TMPFS for the next time at
all.
I might be able to create such a feature myself, but few pointers would be
nice
(which script to look for and which is THE script building a pkg and where
to trap
the error and re-try the compilation).
Or is this functionality already in T2 or is the idea doomed already in the
drawing board?
Thx in advance and thx for great compilation environment,
Mike N
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
