[repost with correct sender]
On 11-Aug-2015 7:51 pm, "Buck Evan" <buck_at_yelp.com> wrote:
> On Mon, Aug 10, 2015 at 11:38 AM, Laurent Bercot <
> ska-supervision_at_skarnet.org> wrote:
> > That's perfectly reasonable.
> > Is this Debian policy that /lib/*.so is in the -dev while
> > /lib/*.so.* is in the runtime package ?
>
> Yes. It's quite explicit.
[ . . . ]
> > If you're developing
> > and want to link against the .so, you need the shared object
> > at compile time anyway, you can't do with just the .so symlink
> > (or can you ?) - so, what's the rationale for separating just
> > that link instead of having all the .so stuff in the runtime
> > package ?
>
> As you say, you want the .so if you're developing.
> If you're "just a user" though, none of your binaries will link directly
to
> that symlink.
> That's the rule of thumb for moving things to the -dev package.
> Possibly the bit you're missing is that x-dev almost always depends on x.
Also, putting the .so in -dev means that libfoo2 and libfoo3 can coexist,
even though libfoo2-dev and libfoo3-dev can't, because they both provide
/usr/lib/libfoo.so.
--
/c
Received on Tue Aug 11 2015 - 18:40:18 UTC