18.06.2013 21:16, KP Kirchdoerfer пишет:
> Hi gents;
>
> libnl and libnl3 has been the source of a great mess in the past.
> libnl has been put in to maintence mode, with libnl2/3 as successor -
> while a lot of packages still relied on libnl.
>
> We've discussed that issue in 2010:
> "IMHO it isn'
Hi gents;
libnl and libnl3 has been the source of a great mess in the past.
libnl has been put in to maintence mode, with libnl2/3 as successor -
while a lot of packages still relied on libnl.
We've discussed that issue in 2010:
"IMHO it isn't good idea to switch on libnl v2 - because it still in
