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

[Andrea Galbusera]

[Sorry, this is a repost: previously forgot to CC the mailing list]

Hi Stuart,
now that CVS repo is up again I'm back getting in confidence with the
BSP release process of ltib.

I'm going on the "local CVS with vendor import from Savannah" way (see
quotation below) for the moment; public uploads may come later on. I set
up a local CVS module by importing the latest sources from Savannah
repo. I then added my patches/configs and followed suggestions in
doc/LtibReleaseProcess, but I still can't use -m release target because
it wants to get packages from gpp. Since for the moment I still don't
want to upload the patches to the gpp, do I have a mean of having the
iso release process to complete with local packages instead?

Thanks for the useful advices.
Regards!
Andrea

On Tue, 2007-03-13 at 15:41 +0000, Stuart Hughes wrote:

> > > 
> > > * If you don't want to use the public CVS to make your BSP available,
> > > I'd recommend that you create your own private LTIB CVS project and then
> > > use the public CVS as the initial (and subsequent) vendor import.  That
> > > way you have a means of keeping your private tree in sync with the
> > > public one.  Also this will allow you to use the normal '-m release'
> > > process that references CVS
> > 
> > This sounds like the most promising solution for me. Just wanted to try
> > it now, but I can't checkout from CVS... I get errors from the site
> > being unable to connect to the database. I'll try later and let you
> > know.
> > > 
> 
> Yes, I tried this morning had it seems like savannah.nongnu.org was
> down.  I just tried and the site is up, but there are still problems.
>