Re: [Ltib] what is the need for the autoconf tools in /opt/ltib/usr/bin?

[Peter Barada]

On 10/31/2011 01:23 PM, Stuart Hughes wrote:
> On 31/10/11 15:24, Peter Barada wrote:
>> On 10/28/2011 03:54 AM, Stuart Hughes wrote:
>>>> Granted I know I'm in a breadline begging for toast, but how can I
>>>> teach ltib to remove a host package if its no longer called out for
>>>> in config/userspace/ltib.preconfig? Then it should be relatively easy
>>>> to disable flex/bison and add them to pre_install_deps, remove
>>>> .host_wait_warning* and the next "./ltib" should clean things up in
>>>> /opt/ltib/user/bin...
>>>>
>>> You can run ./ltib --hostcf --configure and that will let you
>>> configure what goes into the host support packages without having to
>>> touch .host_wait_*
>>>
>>> Be warned though that because it goes through the config system, the
>>> dependencies for packages get evaluated, so some other packages you
>>> didn't expect may get pulled in.
>>>
>>> Note: with --hostcf, you can do all the normal ltib stuff, with a few
>>> provisos.
>> Stuart,
>>
>> If I edit config/platform/host/ltib.preconfig and comment out some
>> packages (like gbison, flex, git) and run "./ltib --hostcf" it doesn't
>> remove the packages from /opt/ltib - it does if I run "./ltib --hostcd
>> --configure", and only after asking me if I want to drop them.  How can
>> I force ltib to drop the host packages that are no longer selected (and
>> not have to run --configure)?
>>
>> I'm trying to automate the build process to handle changes to
>> config/platform/host/ltib.preconfig (as I run LTIB from buildbot).
>>
>>
> Hi Peter,
>
> The ltib.preconfig is for the initial build (defconfig equivalent). 
> If you use --hostcf you have to use it like the normal configuration
> process and run:
> ./ltib --hostcf -m config
> and select the packages you want in the configuration.
>
> In your case for a buildbot, provided you edit ltib.preconfig it
> should do what you expect on the first run (from pristine), after that
> you may need to do some clean-up (can't recall right now).
Unfortunately it doesn't.  looked in /opt/ltib, but couldn't find a copy
of the ltib.preconfig I could use to do a comparison on (and if
different force it to run the --hostcf step).  I'll figure out to add a
flag that tells --hostcf to not ask about dropping a package.

>
> Regards, Stuart


-- 
Peter Barada
address@hidden