On Sat, Oct 03, 2015 at 01:10:18PM +0200, Felix Fietkau wrote:
> > As far as I understood this, libnl-tiny is a drop-in replacement for
> > libnl-core. Or is there a difference in functionality or API/ABI?
> libnl-tiny replaces the most commonly used parts of libnl-core + -genl.
> The API is a bit
On 2015-10-03 10:52, Baptiste Jonglez wrote:
> On Tue, Sep 22, 2015 at 03:42:26PM +0300, Alexandru Ardelean wrote:
>> So,
>> - bmon requires libnl-route
>> - aircrack-ng requires libnl-genl
>> - kismet i am not sure 100% ; maybe libnl-genl ; I did not want to
>> investigate much deeper
>> - ibrcomm
On Tue, Sep 22, 2015 at 03:42:26PM +0300, Alexandru Ardelean wrote:
> So,
> - bmon requires libnl-route
> - aircrack-ng requires libnl-genl
> - kismet i am not sure 100% ; maybe libnl-genl ; I did not want to
> investigate much deeper
> - ibrcommon requires libnl-genl and libnl-route
> - keepalived
On 2015-09-22 14:42, Alexandru Ardelean wrote:
> Anyway, moving forward with the split:
> 1) Do I rename the libnl package to libnl-core and make libnl a
> metapackage that pulls in everything ? or
> 2) Do I leave this structure as is (with the fixes/updates I'll add
> later) and update those packa
On Thu, Sep 17, 2015 at 5:13 PM, Alexandru Ardelean
wrote:
>
>
> On Thu, Sep 17, 2015 at 4:50 PM, Felix Fietkau wrote:
>
>> On 2015-09-17 15:05, Alexandru Ardelean wrote:
>> > From: Alexandru Ardelean
>> >
>> > The idea is that we may only need the libnl core,
>> > or libnl-route or libnl-nf li
On Thu, Sep 17, 2015 at 4:50 PM, Felix Fietkau wrote:
> On 2015-09-17 15:05, Alexandru Ardelean wrote:
> > From: Alexandru Ardelean
> >
> > The idea is that we may only need the libnl core,
> > or libnl-route or libnl-nf libs, but maybe not all of them.
> >
> > This way we can select which ones
On 2015-09-17 15:05, Alexandru Ardelean wrote:
> From: Alexandru Ardelean
>
> The idea is that we may only need the libnl core,
> or libnl-route or libnl-nf libs, but maybe not all of them.
>
> This way we can select which ones we need without bloating the
> firmware image too much.
>
> Signed
From: Alexandru Ardelean
The idea is that we may only need the libnl core,
or libnl-route or libnl-nf libs, but maybe not all of them.
This way we can select which ones we need without bloating the
firmware image too much.
Signed-off-by: Alexandru Ardelean
---
package/libs/libnl/Makefile | 6
