Hi,
2018年10月24日(水) 0:48 Andreas Henriksson <andr...@fatal.se>:
>
> On Tue, Oct 23, 2018 at 08:46:13PM +0900, Nobuhiro Iwamatsu wrote:
> > Hi,
> >
> > > For the record the just released iwd 0.10 supports building against an
> > > external ell (eg. not using the embedded code copy of ell).
> > >
> > > See the --enable-external-ell configure flag (which is still not being
> > > used because of previously mentioned issues).
> > >
> >
> > I just upload ell 0.12, and I test building iwd with
> > '--enable-external-ell' option.
> > Packge building is fine. I attached a patch for support compiling
> > packages with external ELL.
>
> Thanks for testing. Do we want to commit to doing this though?
>
> That will mean:
> a/ you'll need to be on your toes with new versions to not block
> uploading new iwd versions.
> b/ every time you upload a new ell version we'll need to have
> some kind of mini-transition (potentially involving
> debian release team which will not look kindly on libraries
> which do breaking changes without bumping soname/sover).
>
> Most likely I'd say we should generate a very strict dependency
> from iwd on ell, since we know there are now ABI guarantees and
> upstream will thus not bump soname/sover when doing breaking
> changes. That would mean every new ell version would make iwd
> uninstallable until it has been rebuilt (if API is still not
> broken which would require a sourceful upload).
>
> I'm not sure the hassle is worth it at this point.
>
> OTOH, the hassle would be mostly on your side since Debian
> normally frowns on breaking changes and you as ELL maintainer
> would be the one doing those. :P
>
> For now I'm leaning towards postponing this for a while still...
As you pointed out, ell's API is unstable yet.
I agree with your opinion. We do not have to do build-depends of the
Debian package
ell until the ell API is stabilized.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
