RE: [Ltib] Help with ltib and source tree

[Stuart Hughes]

Hi Bizhan,

You can put the commands to do the checkout into the %prep section of
the spec file.  For example for a CVS system (change for your favourite
SCM):

%define buildsubdir ppc-utils-0.0.2-0
Summary     : ppc utilities
Name        : ppc-utils
Version     : 0.0.2
Release     : 0
License     : GPL
Vendor      : Freescale
Packager    : Stuart Hughes
Group       : System Environment/Kernel
BuildRoot   : %{_tmppath}/%{name}
Prefix      : %{pfx}
...

%Prep
cvs -d:pserver:anonymous:address@hidden:/cm/vault/ltib co -d %{buildsubdir} 
%{name}

NOTE: at some release point you should tag and convert to a tarball +
any patches that might be needed post-test.!!!


I'm away for a week now, so I'm afraid I won't be responding to email
until my return.


Regards, stuart


On Wed, 2008-08-27 at 08:18 -0700, Bizhan Gholikhamseh (bgholikh) wrote:
> Hi Stuart,
> Here is what I am hoping to establish, to use ltib for configuring
> different kernel version for different platform type.
> The source code for ramdisk will have a common section (packages) for
> all platforms and specific packages to each platform. Using ltib, I can
> create a source tree by this command: ltib -p <package name> -m <prep>
> from a package spec. However, at this time I would like to create the
> source tree by checking out the files from a subversion source tree.
> This I am not sure how to do?
> 
> Any hint greatly appreciated.
> Many thanks in advance,
> Bizhan
> 
> 
> 
> > -----Original Message-----
> > From: Stuart Hughes [mailto:address@hidden 
> > Sent: Wednesday, August 27, 2008 1:06 AM
> > To: Bizhan Gholikhamseh (bgholikh)
> > Cc: address@hidden
> > Subject: Re: [Ltib] Help with ltib and source tree
> > 
> > Hi Bizhan,
> > 
> > First of all LTIB is not a SCM system.  It's really a 
> > publishing system that allows the same Linux system to be 
> > reliably reproduced.  It is also configurable (you can 
> > add/removed packages etc).  There is a lot more information 
> > here:  http://bitshrine.org
> > 
> > I'm not really sure I understand your question.  The packages 
> > in LTIB are standard open source packages and aside for some 
> > minor patches that are needed (usually) for cross compiling, 
> > nothing is changed in their source trees.
> > 
> > Are you trying to maintain your own set of package (e.g. ones 
> > you wrote yourself)?
> > 
> > Regards, Stuart
> > 
> > On Tue, 2008-08-26 at 17:53 -0700, Bizhan Gholikhamseh 
> > (bgholikh) wrote:
> > > Hi All,
> > > As part of the software release and development, we are 
> > looking to see 
> > > whether we can leverage from ltib.
> > >  
> > > In our existing environment we are maintaining source code for more 
> > > than 200 developers using a non-open source tool chain.
> > > The source codes are maintained by subversion. Each developer must 
> > > first to checkout entire source tree and build the source 
> > tree through 
> > > scripts that are provided. At that time all the source 
> > files have been 
> > > check out, they can modify each file and check back only 
> > the the files 
> > > that they have modified. Very simple and nothing fancy.
> > >  
> > > Now our development is becoming more complex, we are going to use 
> > > different platform and want to use the same source tree. We 
> > also need 
> > > better way to manage our build environment.
> > > I am looking at ltib to help us to manage this complexity, 
> > however, I 
> > > am not sure how I can use svn and ltib to maintain a source 
> > revision 
> > > of source trees.
> > >  
> > > I appreciate if you could provide me with some hint and pointers.
> > >  
> > > Many thanks in advance,
> > > Bizhan
> > > _______________________________________________
> > > LTIB home page: http://bitshrine.org
> > > 
> > > Ltib mailing list
> > > address@hidden
> > > http://lists.nongnu.org/mailman/listinfo/ltib
> > 
> > 
> 
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib