Re: Library package naming
Roger Leigh <rl117@york.ac.uk> immo vero scripsit:
> However, the value of having a shared library at this point in time is
> doubtful. gimp-print will Build-Depend on it, and possibly hpijs, but
> I don't think there will be many other users. I don't think that the
> effort of packaging it as a shared library is worth the benefits right
> now. The library is tiny, so it isn't going to gain much in reduced
> memory usage.
Don't underestimate the significance of a shared library in
Debian.
> I think I will use Sean's suggestion and have a static-only ijs-dev,
> and once the specification and ABI are stable I will then make it
> shared.
I really doubt you've read my notes enough, but anyway.
Make sure it doesn't get released in stable.
Whatever it is, and however much you claim it is an unstable ABI,
if it gets released as a "stable" Debian release,
it will be stable for a long time.
regards,
junichi
--
dancer@debian.org : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Libpkg-guide: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/
--
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: