RE: Re: [Ltib] ltib doubt

[Zahidul Haque]

Thanks a lot for yours quick reply.

I got to understand a lot about the download point of the packages.

When I open ltib it shows $bdir = "/opt/freescale";  and    lpp          => 
"$bdir/pkgs",

So anyhow it should get the package even for the first time for my LPP. (i.e 
/opt/freescale/pkgs) but that is not happening. Also as you have mentioned that 
once it does not get the packages from LPP it will go to GPP. But in that case 
it should fail as in my case the package is just a test package which should 
not be in GPP.

I am attaching my spec file herewith. Kindly check whether the spec file is Ok 
or not as still I am not able to figure it out as where I am wrong??



________________________________________
From: address@hidden address@hidden On Behalf Of Mike Goins address@hidden
Sent: Friday, April 16, 2010 11:03 PM
To: address@hidden
Subject: Re: Re: [Ltib] ltib doubt

On Fri, Apr 16, 2010 at 1:23 PM, Miguel Aveiro
<address@hidden> wrote:
> Well,
>
> I according to the FAQ from LTIB site
> (http://ltib.org/documentation-LtibFaq), LPP is the first place where it
> looks when compiling, then PPP and then GPP.
>
> It seems the problem is that the default place for LPP is /opt/ltib/pkgs.
> Even if you placed your package in /opt/freescale/pkgs, it will first look
> in /opt/ltib/pkgs and it will not find it, then will download from GPP
> (http://www.bitshrine.org/gpp/) and then compile. The second time you do
> that, the package will be in /opt/ltib/pkgs, and it compile faster.
>
> I looked in the ltib program (just go to ltib directory and open ltib with
> gedit) and has the define of the place where it looks for lpp:
>
>     bldbase      => $top,
>     rpmipfx      => '/',
>     rpmdb        => '/var/lib/rpm',
>     rpmdir       => "$top/rpm",
>     _rpmdir      => "$top/rpm/RPMS",
>     rpm          => "$bdir/ltib/usr/bin/rpm",
>     rpmbuild     => "rpmbuild",
>     sudo         => "sudo",
>     dodrop       => 'yes',
>     prefix       => "/usr",
>     sysconfdir   => "/etc",
>     localstatedir=> "/var",
>     noscripts    => "--noscripts",
>     mandir       => "share/man",
>     tmppath      => "/tmp/ltib",
>     projtmp      => "$top/tmp",
>     bin_path     => "$top/bin",
>     defpfx       => "$bdir/ltib",
>     lpp          => "$bdir/ltib/pkgs",
>     spoof_path   => "$bdir/ltib/usr/spoof",
>
> Well, I hope that was what you asked. Maybe I misunderstood.
>
> Miguel Aveiro


Most all the settings can be overridden in .ltibrc:
http://www.bitshrine.org/autodocs/LtibFaq.html#ref_95



> Em 16-04-2010 10:38, Zahidul Haque escreveu:
>
> Hi All,
>
>
> I am trying to add a new package to the ltib and trying to build the
> package. I have been succesfull in adding in to the directory structure of
> ltib. But I have a got few doubts.
>
> The first time I configure ltib it takes a lot of time to extract the
> package by displaying the following on console:
>
>
> Processing: test-package
> ======================
> Build path taken because: force set, build key set, no prebuilt rpm,
> Testing network connectivity
>
>  Only After after a few minutes it extracts the source and starts building.
> What I feel it looks for the package in GPP or PPP but not in LPP. Although
> my package resides in /opt/freescale/pkgs.
>
>  So my doubt is how to make the default behavior to point to LPP which
> should always be the case. But this happens only the first time I confgiure
> ltib.
>
>  Kindly help me


_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."

add-package.spec
Description: add-package.spec