On Fri, 2017-12-29 at 23:52 +0100, Andreas Henriksson wrote:
> Control: tags -1 = wontfix
> 
> Hello Evgenii Smirnov,
> 
> On Mon, Dec 11, 2017 at 07:19:27PM +0100, Evgenii Smirnov wrote:
> > Package: iproute2
> > Version: 4.3.0-1ubuntu3.16.04.2
> > Severity: wishlist
> > Tags: patch
> > 
> > ip link tool has an ability to use external shared libraries for 
> > defining custom device kinds which will be managed by the tool.
> > To build such libraries three header files are needed. It would 
> > be great to provide this headers in a dev package.
> 
> There used to be an iproute-dev package, which was removed by me.
> There where no legitimate users, only abusers of this internal code
> which is not a proper library to export as is for external
> consumption.
> Also the internal libnetlink is as far as I know being phased out
> even for internal iproute2 usage in favour of libmnl.
> The existing users where ported over to libmnl where needed when
> the iproute-dev package was removed.
> I would suggest you base your own code around libmnl where possible
> and if you're really modifying the iproute2 internals, then do that
> by patching the iproute2 source (via debian/patches/) and rebuild
> the package from source. If libnetlink is not yet fully phased out
> in upstream iproute2 I'm convinced your help in porting it over to
> libmnl is welcome as well! :)
> 
> I'm thus tagging this bug report as wontfix based on the historical
> information and suggesting that it should be closed (but both of
> these are really up to the new maintainers to decide on).
> 
> Regards,
> Andreas Henriksson

Hi,

Personally I agree with your point of view - I wouldn't really be too
keen to maintain downstream some internal headers for public usage -
having to counter API breakages and so on.

If upstream committed to publish a public header, with all the
guarantees this would entail, that would change things - but I don't
see that happening.

If Alex also agrees then we'll close this.

-- 
Kind regards,
Luca Boccassi

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to