[oe] [meta-oe][PATCH 1/2] iproute2: add bbappend for supporting tipc tool

[Randy MacLeod]

On 2017-08-18 02:10 AM, Yi Zhao wrote:
> 
> 
> 在 2017年08月17日 22:01, Khem Raj 写道:
>> On Wed, Aug 16, 2017 at 11:40 PM, Yi Zhao <yi.zhao at windriver.com> wrote:
>>> The tipcutils 2.2 removed the tipc-config tool and recommended to use
>>> the new configuration tool named "tipc" in iproute2 package for
>>> configuring the tipc, which utilizes the new tipc netlink kernel API.
>>>
>>> We supported tipc in iproute2 with PACKAGECONFIG in oe-core commit
>>> 944ef0de241de77429ab0e5cb1dd4a7f355cf3fd
>>>
>>> Add iproute2 bbappend to enable tipc for tipcutils.
>>>
>>> Signed-off-by: Yi Zhao <yi.zhao at windriver.com>
>>> ---
>>>   meta-oe/recipes-connectivity/iproute2/iproute2_%.bbappend | 2 ++
>>>   1 file changed, 2 insertions(+)
>>>   create mode 100644 
>>> meta-oe/recipes-connectivity/iproute2/iproute2_%.bbappend
>>>
>>> diff --git 
>>> a/meta-oe/recipes-connectivity/iproute2/iproute2_%.bbappend 
>>> b/meta-oe/recipes-connectivity/iproute2/iproute2_%.bbappend
>>> new file mode 100644
>>> index 0000000..0869f7f
>>> --- /dev/null
>>> +++ b/meta-oe/recipes-connectivity/iproute2/iproute2_%.bbappend
>>> @@ -0,0 +1,2 @@
>>> +# For tipcutils
>>> +PACKAGECONFIG_append = " tipc"
>> can we do it in recipe proper itself ?
> 
> Hi Khem,
> 
> The tipc in iproute2 needs libmnl as dependency.  Currently libmnl is in 
> meta-networking and there are some packages in meta-networking need it 
> as dependency, so we can not enable tipc build in oe-core directly.
> If we want to enable it in iproute2 recipe directly, we should move 
> libmnl to oe-core. I don't know if it is worth to do that because few 
> people need tipc. How do you think about it ?

We should move libmnl and the iproute2 change to oe-core.

By default, TIPC is enabled as a module in YP kernel:

$ grep TIPC 
tmp-glibc/work/qemuppc-oe-linux/linux-yocto/4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0/linux-qemuppc-standard-build/.config
CONFIG_TIPC=m
CONFIG_TIPC_MEDIA_UDP=y

so it should be configurable with just the oe-core layer.

Once libmnl is in oe-core, we could move nftables,
"the successor to iptables" to oe-core say at the start of
the 2.5 dev cycle.

../Randy

> 
> Thanks,
> Yi
> 
>>
>>> -- 
>>> 2.7.4
>>>
>>> -- 
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel at lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> 


-- 
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, 
Canada, K2K 2W5