Re: [Ltib] Preparing a source release ISO for GPL requirements

[Stuart Hughes]

Hi Jim.

I've only got time to answer briefly, but yes ./ltib -m release is what
you want.

When you run this, all the sources referenced by the default BSP
configuration and all dependencies (toolchains set) will get copied onto
the ISO image in the pkgs directory.

Normally the release script expects these sources to be available on the
GPP (it's a checked to make sure it's distributable).  However there is
(not sure about 9.1.1) -m trelease which bypasses some checks.

If your code does not match what's on CVS you will have to give the
option 'localdir' (I think) when prompted for the release tag.  This
will read the ltib source (making the references) from a file called
MANIFEST that you must generate from your local code tree.  There's a
helper script for this in bin/cvsmanifest which you can run against the
pristine code base and then tinker with (comments in file).

Hope this helps a little.

BTW: If your source are not too old you could make a local git tree from
your source base and release against this.  Later ltib's understand git
trees for releases (although not tested that much).

Regards, Stuart

On 26/08/11 20:23, Jim Barlow wrote:
> Hello Stuart,
> 
> I'm looking for a way to release LTIB and along with the source for all
> GPL packages we use. This is to fulfill our GPL requirements of
> releasing all of the changes we've made. We've introduced a number of
> new packages and patches, tweaks to .spec files and LTIB script itself,
> and significant kernel modifications to support our hardware. Since a
> GPL release is supposed to be buildable I like the idea of releasing
> using LTIB rather than handing off a bunch of spec files and packages. 
> 
> I'd prefer to make the release independent of the GPP or any other
> external resource, mainly to minimize support requests if bitshrine.org
> is down, etc.
> 
> It seems that the command "./ltib -m release" is structured for a binary
> release. The /pkgs folder on the ISO is empty. From what I've read it
> seems like "-m release" is more for internal distribution than a public
> release. Does LTIB have a facility for doing what I want? How would I go
> about doing that? I'm using an older LTIB by the way: 9.1.1 (1.445.6.1)
> from a Freescale ISO dated December 2009.
> 
> Thanks for all the hard work you've put into maintaining LTIB.
> 
> Jim Barlow
> IVL Audio Inc
>