Hi Christian,
No, didn't change anything. But I guess it was related to a
"close-to-disk-full" situation with slow i/o.
hm, interesting. I would expect that "disk-full" causes problems, but
not "close-to-disk-full" ;-)
The process does not wait endless. In the moment there is a lock time of 1
hour. If the lock file of a specific process exists for one hour, another
process is allowed to remove it, assuming, that the first process is no
longer alive. Packaging of one package should never take one hour ;-)
Ah, I'm way too impatient for that - a en-US build is completed in
less than one hour on that machine :-)
I see, for your scenario waiting one hour is not a good value. But for
nightly builds it is very comfortable.
The idea of the package pool is, to use the same packages for different
products. If you create an English OOo installation set and later you want a
German OOo installation set, than only the language dependent packages have
to be created. So the creation of the German installation set will be very
fast.
Ah, OK thanks for the explanation - but "very fast" is relative :-)
So when I only create en-US full installset (and only do languagepacks
for the other languages), the packaging will never make use of the
pool?
The package pool is filled, if you create more and more installation
sets. If you have to create every package exactly once, the package pool
cannot offer any advantage for you. But typically packages are created
more than once, because you create an installation set a second time, or
because you make a further installation set, that uses the same
packages. If you know, that you do not need the pool, simply set the
property POOLPRODUCT to 0.
Ciao
Ingo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
