Re: [Ltib] installing the /opt/ltib structure?

[Stuart Hughes]

On Tue, 2009-03-03 at 05:52 -0500, Robert P. J. Day wrote:
> On Tue, 3 Mar 2009, Stuart Hughes wrote:
> 
> > Hi Robert,
> >
> > The content (source/patches) are supposed to be completely
> > independent of the tool itself.  So normally to move a project I
> > would do this:
> >
> > $ ./ltib -m distclean
> > $ cd .. ; tar zcvf my_ltib.tar.gz _ltib_
> >
> > and then copy to the target machine and untar it and run ./ltib and
> > let it built the platform you want.
> 
>   the current issue is that i'm assuming you're referring to running
> that "ltib" command in the directory corresponding to the expanded
> tarball of whatever version of ltib the original installer used.
> which i don't have in front of me at the moment.  i'm working with an
> already-installed ltib and i don't see the original tarball that was
> used (although i'm fairly sure it was 6.4.1).

Working with an already install LTIB is okay, so long as it's the one
you want to clone.  You simply need to do:

$ ./ltib -m distclean   

This cleans it up to a state that you can then tar up and put on another
machine.  You don't need to original installer necessarily.

> 
>   so i just want to confirm that you're assuming i had that directory
> in front of me, and that it would contain the results of that initial
> configuration and install, correct?
> 

No, just a working copy.  However if you're using this for anything
other than personal use I'd recommend using some know version (from
Savannah CVS).

>   also, i recall that you clarified this once upon a time, but where
> should the results of running "./ltib" be placed.  depending on what
> you read, it's either /opt/freescale or /opt/ltib.  was one the old
> location and the other the new location?  how did that work?  thanks.
> 

The stuff that goes into /opt comprises 2 things:

/opt/_prefix_/pkgs   : this is the package content cache
                       which can be shared across projects/users

/opt/_prefix_/....   : all the rest is common host support content 
                       built by ltib, such as wget, mkfs.jffs2 etc

The actual prefix is /opt/freescale for BSP ISO releases from Freescale.
I cannot directly support these (refer back to Freescale)

For Savannah derived BSPs, the common areas are /opt/ltib/....

Note that Savannah LTIB knows to look in /opt/freescale/pkgs for package
content (to save downloading again).

Note: the reason for keeping these separate is purely practical as it
allows me concurrently to have both types installed without interfering
with each other.

Regards, Stuart