Re: [Ltib] Archiviation method for a project developed using ltib

[Stuart Hughes]

Hi Claudia,

I wouldn't recommend putting a built project under subversion or other
SCM system.  If you record an exact date tag of the copy of CVS you are
using plus any changes you have made, that's all you need.

LTIB itself is under SCM using CVS and so any version can be re-created.
The source/patches are separately help on the gpp
(http://bitshrine.org/gpp) and this is a permanent archive of immutable
files.  What I mean is that filename X will never be overwritten with
different content.  The idea is that you can always re-create an LTIB
from any point in its history.

If you do want to save an encapsulated copy with LTIB + built packages +
sources and patches, then run ./ltib -m release.  This will make an iso
image.

BTW: if you are using an MMUless platform I would recommend using
uClinux-dist (http://www.uclinux.org/pub/uClinux/dist/)  in the case of
MMUless platforms (only), uClinux-dist has far more packages available.

Regards, Stuart

On Fri, 2007-07-06 at 10:35 +0200, Claudia De Bartolomeis wrote:
> Hi everybody,
> I'm developing an application under uClinux using ltib,
> and now I have to choice an archiviation method .
> 
> address@hidden:~> du -hs *
> .........
> 615M    ltib-m532xevb-20061117
> ........
> Till now I have been using subversion 1.1 with subclipse under eclipe,
> but
> my ltib working dir is huge,
> and I'm not sure this way is suitable.
> 
> Any suggestion for a project archiviation method ?
> Thanks in advance 
> Claudia
> 
> 
> 
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib