[Developers] cactus feature request: source code saves

[Erik Schnetter]

On Tuesday 24 May 2005 19:20, Frank Loeffler wrote:
> Hi,
>
> Erik Schnetter wrote:
> > The working principle is as follows.  When thorn Formaline is
> > compiled, it creates a tarball of all source code that goes into
> > the executable,
>
> Let me first thank you for this, this is really a good idea. As
> addition one could/should also save config-info and the thornlist
> this way.

Good idea.

> What happenes in the case when I recompile other thorns because if
> changes in them? Would that mean these changed would not be included
> in the tarball?

No, the tarball is recreated each time the final executable is linked.

One obvious optimisation is to create one tarball per thorn, so that 
small changes lead to less work.  That would require changes to the 
flesh, though.

-erik

-- 
Erik Schnetter <schnetter at aei.mpg.de>   http://www.aei.mpg.de/~eschnett/

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.cactuscode.org/pipermail/developers/attachments/20050524/3f0e1b28/attachment-0002.bin