On 07/19/2015 11:06 AM, Eduard Bloch wrote:
> ... even if there are no users who care! And won't care in
> future because it's clear that upstream is not using a stable API.
since the sceintific community was mentioned as the background for these
users: i doubt whether they won't care *because* it
On Sun, Jul 19, 2015 at 11:06:45AM +0200, Eduard Bloch wrote:
> > > It's less of a library than an environment used for research. Compiling
> > > is just a required step to run your code, but applications are usually
> > > not distributed in binary form.
> >
> > What is the benefit of providing a
Hallo,
* Bas Wijnen [Sun, Jul 19 2015, 04:10:21AM]:
> On Fri, Jul 17, 2015 at 05:30:04PM +0200, Ansgar Burchardt wrote:
> > It's less of a library than an environment used for research. Compiling
> > is just a required step to run your code, but applications are usually
> > not distributed in binar
On Fri, Jul 17, 2015 at 05:30:04PM +0200, Ansgar Burchardt wrote:
> It's less of a library than an environment used for research. Compiling
> is just a required step to run your code, but applications are usually
> not distributed in binary form.
What is the benefit of providing a shared library a
On 2015-07-17, Ansgar Burchardt wrote:
> So, I still plan to drop the extra library packages and just move the
> shared library to libdune-*-dev.
I'd suggest you set it up with shlibs that ensures that packages built
against these libraries aren't installable in the archive.
/Sune
--
To UNSUB
Hi,
On 07/09/2015 06:39 PM, Bas Wijnen wrote:
> On Thu, Jul 09, 2015 at 05:26:32PM +0200, Ansgar Burchardt wrote:
>> I'm wondering about the shared library packaging requirements in Policy
>> for the special case of scientific libraries that are not intended to be
>> used by applications, but are
Hi,
On Thu, Jul 09, 2015 at 05:26:32PM +0200, Ansgar Burchardt wrote:
> I'm wondering about the shared library packaging requirements in Policy
> for the special case of scientific libraries that are not intended to be
> used by applications, but are to be used by end-users directly,
What does "t
Hi,
I'm wondering about the shared library packaging requirements in Policy
for the special case of scientific libraries that are not intended to be
used by applications, but are to be used by end-users directly, and that
do not have a stable ABI.
In particular does splitting out the shared libra
8 matches
Mail list logo
