Re: [Ltib] how to create a stand alone iso?

[Stuart Hughes]

If you check out the latest from Savannah CVS, you have it under some
control.  You just can't commit your changes (as they may not be
general).  However you can maintain a patch with 'cvs diff'.  This is
for the ltib tool only.  If you want to have your own writable CVS,
you're on your own.  You can do it, but you should use cvs import to
regularly do vendor branch imports (from Savannah).  If you don't know
how to do this, you can find docs on CVS on the internet.

So far as the content goes, that is just a set of files on an http
server, so there is no source control required.  You can add your own
tarballs/patches to your local /opt/ltib/pkgs and/or keep a private PPP
server to make them available centrally.

It sounds to me like you don't need to do anything with ISO images.

Regards, Stuart

On Wed, 2008-09-17 at 16:32 +0530, Anirudh Venkataramanan wrote:
> I am not able to understand how this release option actually works.  I
> did the cvup and generated the MANIFEST file as mentioned. I tried to
> do a cvs commit but it failed saying I don't have CVS write
> permissions. Why is it necessary to commit to make a release?
> 
> Just in case I sounded a little vague last time, the requirement is
> something like this. I want to start with baselined ltib and packages
> at my local CVS. after this whatever development I do, I do it from
> CVS. This might include adding new packages to the BSP, or making
> changes in the baseline itself (kernel hacks, new drivers etc).
> Whatever changes I make from the ISO stage, I want to source control.
> 
> 
> 
> 
> 2008/9/17 Stuart Hughes <address@hidden>
>         Hi Anirudh,
>         
>         Yes you can, but you should not be checking in content (e.g.
>         stuff from
>         the GPP like tarballs) into CVS.  You cannot by definition
>         source code
>         manage them.  Also you should not be making a CVS of a CVS,
>         this is a
>         recipe for a disaster, you'll never be able to get support for
>         this as
>         I'd have no idea what you have.
>         
>         To download anything currently referenced by your LTIB
>         configuration
>         without building run:
>         
>         $ ./ltib --dlonly
>         
>         To make an iso image you can run:
>         
>         $ ./ltib -m release
>         
>         You may need to use:
>         
>         $ ./ltib -m trelease
>         
>         To defeat some of the checking mechanisms.  I've not tried to
>         make an
>         ISO from Savannah before.
>         
>         However this only works if the content is on the GPP and in
>         Savannah
>         CVS. If not, you'll have to provide a MANIFEST file, take a
>         look at
>         bin/Ltibrelease.pm to get an idea of what is going.  I've
>         checked a file
>         into CVS for generating the MANIFEST file, run it with:
>         
>         $ bin/cvsmanifest > MANIFEST
>         
>         You will then need to edit that file to prune/add files that
>         you want to
>         go into the released ISO image.  Note this ISO image will also
>         included
>         any package content (it gets put into a pkgs directory).
>         
>         
>         Regards, Stuart
>         
>         
>         On Wed, 2008-09-17 at 11:49 +0530, Anirudh Venkataramanan
>         wrote:
>         > is it possible to download all source tar balls and patches
>         from gpp
>         > once and create a stand alone iso that wont download from
>         GPP? I would
>         > like to do this so that I can baseline ltib and upload it to
>         my CVS.
>         >
>         > If possible, can anyone please suggest how?
>         >
>         > --
>         > Regards,
>         > Anirudh Venkataramanan
>         >
>         
>         > _______________________________________________
>         > LTIB home page: http://bitshrine.org
>         >
>         > Ltib mailing list
>         > address@hidden
>         > http://lists.nongnu.org/mailman/listinfo/ltib
>         
> 
> 
> 
> -- 
> Regards,
> Anirudh Venkataramanan
>