Sorry for the no subject on that email, just forgot. Well, in my case I
was using the per-platform pkg_map as you say in option "2/", where I was
adding two new packages. They just weren't obeying the order I was used
to working with the other pkg_map where I list the one I want to build
first, so I was getting a little confused.
> Hi Aaron,
>
> You can user the per-platform pkg_map to
>
> 1/ Override the .spec file that will be built for a given package name.
> The idea is to allow you to build a different version than the stock
> package.
>
> 2/ You can add new packages: ones that are not already mentioned in the
> config/userspace/pkg_map. For these packages, you have control over the
> order.
>
> By design, you can't override the build order of the existing packages.
> These are supposed to be correct, or at least the best overall
> compromise.
>
> If you think the order of any packages are incorrect, then please let us
> know your thoughts.
>
> Regards, Stuart
>
> On 16/08/12 20:45, Aaron Wegner wrote:
>> Hi Stuart, I know that I can use
>>
>> ltib/config/userspace/pkg_map
>>
>> to control the build order, and it might be something wrong in my
>> configuration or I'm using an older LTIB (I don't think it's all that
>> old), but I don't seem to be able to control the build order with the
>> file
>>
>> config/platform/${platform}/pkg_map
>>
>> PKG_FIRST = first
>> PKG_SECOND = second
>>
>> I have entries like the above, and second is getting build before first
>> every time.
>>
>>
>> Thanks,
>>
>> Aaron
>>
>>
>> _______________________________________________
>> LTIB home page: http://ltib.org
>>
>> Ltib mailing list
>> [email protected]
>> https://lists.nongnu.org/mailman/listinfo/ltib
>>
>
_______________________________________________
LTIB home page: http://ltib.org
Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib
