Re: [Ltib] making ISO release (aka -m release)

[Stuart Hughes]

Hi Andrea,

You're right (in a way).  In which case you need to either remove the
dltest section (I don't recommend this).

Probably the best thing to do is to setup your own local
(company/department) http server as a 'PPP server'.  Your private
patches should be uploaded there.  Once you have your patches there, you
need to update your local CVS's .ltibrc to reference this server using
the %ppp_url tag.

There is nothing magical about a PPP/GPP server, they are just http.
Provided you can do  wget <base_url>/filename you're home and dry.  Note
as well as putting your patches on the server, each one should have a
corresponding .md5 file.

This might seem like a bit of an overhead, but in the long run if you do
it, you'll be glad you did.  It will make a permanent record of your
patches and a way of easily distributing them within your company before
you're ready to push them into the public domain.

Regards, Stuart

On Tue, 2007-03-20 at 16:55 +0100, Andrea Galbusera wrote:
> Stuart,
> I'm not using neither "localdir" nor "localdir_nobuild". Since I moved
> my ltib sources under a local CVS repository, I thought these two secret
> tags were not required. I also digged the code and saw the attached
> lines and trying to make a release short-circuiting the --dltest call:
> just as a proof of fact I can get to the iso image. Still baking it!
> 
> As far as I understand there is no way to have local-only source
> packages/patches, even if ltib sources are now managed by local CVS and
> being able to make a release without modifying ltib script itself.
> Correct?
> 
> Regards,
> Andrea
> 
> On Tue, 2007-03-20 at 15:13 +0000, Stuart Hughes wrote:
> > Hi Andrea,
> > 
> > When you ran the release, what tagname did you give when prompted?
> > 
> > It needs to be 'localdir' if you want it to run purely from a local
> > MANIFEST file.
> > 
> > If you look at ltib around line 1164 you should see:
> > 
> > # do a dltest to make sure that all files have been uploaded
> > if [ "$tag" != "localdir" -a "$tag" != "localdir_nobuild" ]
> > then
> >     ./ltib --dltest
> > fi
> > 
> > The intention of this is to run the dltest only if the tag is not
> > 'localdir' or 'localdir_nobuild'
> > 
> > Regards, Stuart
> > 
> > On Tue, 2007-03-20 at 12:07 +0100, Andrea Galbusera wrote:
> > > Hughes,
> > > 
> > 
> > > > * The GPP should only be being accessed for files that are not already
> > > > in your /opt/ltib/pkgs directory.  This is correct behaviour.  Not only
> > > > are the packages you have selected copied into the iso image, but also
> > > > the ones that are selectable.  The idea is to be able to provide a
> > > > self-contained iso image for people that may not have any network
> > > > access.  This means that you will need to have a working connection to
> > > > the GPP when you make the release, but you do not need to upload your
> > > > private patches to the GPP (as they'll already be local).
> > > 
> > > My patches are in /opt/ltib/pkgs but running ./ltib -m release I get
> > > errors on, I suppose, the dltest step. Below is the printout. What am I
> > > missing?
> > > 
> > > > [...]
> > > > Testing gpp_url connectivity: OKAY
> > > > OK GPP: tc-mtwk-x86lnx-603e-3.4.3-1.i386.rpm
> > > > 
> > > > Processing platform: LTIB: MPH C4000 target board (based on Freescale 
> > > > MPC5200 targets)
> > > > ========================================================================================
> > > > using config/platform/c4000/.config
> > > > 
> > > > Processing: fake-provides
> > > > ===========================
> > > > 
> > > > Processing: kernel-2.6.16-c4000
> > > > =================================
> > > > OK GPP: linux-2.6.16.tar.bz2
> > 
> > > > OK GPP: linux-2.6.16-mpc5200-0017-codetest-support-07Jul2006.patch
> > > > FAILED: linux-2.6.16-c4000-ethernet.patch 404 Not Found
> > > > FAILED: linux-2.6.16-c4000-uarts.patch 404 Not Found
> > > > FAILED: linux-2.6.16-c4000-jffs2.patch 404 Not Found
> > > > FAILED: linux-2.6.16-c4000-headio.patch 404 Not Found
> > > > 
> > > > Processing: dev
> > > > =================
> > > > OK GPP: dev-1.1.tar.gz
> > > > 
> > > > [...]
> > > > 
> > 
> > 
> > 
>