Re: [Ltib] Relative path in .ltibrc

[Stuart Hughes]

Hi Mattias,

You can't put in a relative path for the value of %lpp.  This is
deliberately so as any files in there should be the same for all users
(on that host).

The source/patches in the LPP/GPP are intended unique and common and
available once you've finished work and want to *publish*.  Effectively
the spec files publish the set of files that make up a package.

Probably for what you want to do you're better off checking out under
revision control, you package under rpm/BUILD.  Let's say your package
is call x, you could do:

$ cd rpm/BUILD/
$ rcs co x           # my guess

Then each developer would work in their own instance of LTIB,
rpm/BUILD/x and check in/out changes as you work.

To make use of this simply use a spec file that doesn't reference any
sources.

Once you're software development is finished, tag your work and then
make a tarball of it and then put that into the LPP/GPP and then create
a proper spec file that references that tarball.

Note: the main thing to understand here is that LTIB is intended more as
a package publishing tool, not a software development tool so it should
not be used for revision control.  However if you use it as indicated
above, it should work well for you.  

BTW: for the Linux kernel, there is a directory build option which
allows you to point at any directory, which may be using
git/cvs/bitkeeper.  You may like to take a look at how this works as
it's similar (but more complicated) that what you are trying to do.  

Regards, Stuart

On Tue, 2007-05-29 at 08:52 +0200, Mattias Boström wrote:
> Hi,
> 
> We're planning on using a build server for a number of developers
> building applications for a custom mpc5200-card. We are using Subversion
> as our revision control system. We would like to handle our own patches
> in the RCS. In order to avoid conflicts between patches generated or
> checked out by the developers we would like to use a local directory,
> unique for every developer, in addition of the /opt/freescale/pkgs
> directory used for global packages.
> Is it possible to use a relative path in .ltibrc or use a environment
> variable?
> I have tried setting %ldirs to ./local_pkgs. The result is that a
> symbolic link is created in the rpm/SOURCES directory for the patch,
> pointing to ./local_pgks/xxx.patch. I can make another symbolic link
> from rpm/SOURCES/local_pkgs pointing to the directory where i wanted it
> originally (../../local_pkgs).
> I would rather avoid symbolic links and specify directly in .ltibrc
> where I wan't to find the patches. Since this value for %ldirs can't be
> the same for every developer we will need to have a relative path or
> maybe something like /opt/$(USER)/pkgs.
> Any suggestions? 
> 
> Regards,
> Mattias Boström
> 
> 
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib