ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] Multi-user LTIB


From: Ken Gilmer
Subject: Re: [Ltib] Multi-user LTIB
Date: Tue, 5 Feb 2008 15:44:28 -0500


Hi Peter,

Thanks for your detailed response! Yes I agree that in general there should not be issues with multiple LTIB instances on a box, but there is one case that we have in particular that could be a problem. We are building our own packages. We have our own spec file (LTIB_HOME/dist/lfs/) and our own private package pool. AFAIK LTIB will seek out packages not in /opt/freescale/packages from the PPP and place them there. Since this is a shared location one developer could assume a certain state for that directory when in fact another developer, using their own instance of LTIB, could clear out (causing the PPP to be queried again) or change that package. This would effect the original developers results and would also be difficult to track down. If it is indeed only /opt/freescale/* that is global, it may not be difficult to do a global search and replace throughout LTIB to try to move it to LTIB_HOME/freescale/*. The funny thing is I thought this is how it used to work (roughly a year ago).

thanks
ken

On Feb 5, 2008, at 2:42 PM, Peter Barada wrote:

On Tue, 2008-02-05 at 14:31 -0500, Ken Gilmer wrote:
Hello :)

   We use LTIB extensively and it is working well for us.  Once pain
point we have is that we have one build machine that is rather
expensive/fast that multiple users are building on.  AFAIK LTIB
stores some state in machine-global locations (such as /opt/
freescale).  While we haven't been burned yet I'd sleep easier at
night if all state for ltib was kept inside it's install directory,
insuring that two different users didn't clobber each other.  I've
played around with variables in the script but my modifications cause
LTIB to break.  Is there a recommended approach or strategy to safely
keeping LTIB instances isolated on a given machine?

I've gone through this with multi-users developing in LTIB before with
little trouble.  since the only thing kept in /opt/freescale/packages
are the tarballs and patches, the spec files that are modified with
"./ltib -p <pkg> -m patchmerge" are within the user's install area,
leaving the only potential problem being if two people do a patchmerge
to the same package at the exact same second (causing the same patch
file to be created for each person's changes). That is a remote chance,
especially if you have people working on different packages.

All of the configuration information (.lkc, .config, .spec, etc) files
are kept in the install directory which is unique to each developer.

Merging those together can be done by hand, kinda a hassle, but
definitely doable.

I don't know of how to keep any modifications to /opt/freescale/pkgs
local to a given user/installation directory.

--
Peter Barada <address@hidden>





reply via email to

[Prev in Thread] Current Thread [Next in Thread]