Hi Niko,
On Sun, Nov 17, 2019 at 04:39:46PM +0200, Niko Tyni wrote:
> at the last tech-ctte meeting the question came up of whether there's
> a general rule in Debian about libraries/modules depending (or not)
> on the corresponding interpreters for their implementation language.
You've already m
On Sun, Nov 17, 2019 at 04:39:46PM +0200, Niko Tyni wrote:
> - for Ruby I only found guidance about application dependencies [2]
> but not module dependencies. The standard library seems to come
> with the interpreter here, so that's not a reason to depend on the
> interpreter package. Still,
> It would be nice to get some input on this.
For Java the library packages never depend on the runtime. Only the
applications depend on a runtime package (typically java[0-9]+-runtime |
default-jre).
And in general we avoid mentioning the dependencies provided by the
environment executing the c
Niko Tyni writes:
> It's not obvious to me what the ideal setup here should be, when there
> are no other reasons for such a dependency than 'need an implementation
> of the language the library is written in'.
I think there can be another reason: "needs a minimum version of the
interpreter langua
> On 17 Nov 2019, at 22:39, Niko Tyni wrote:
>
> - for PHP, there apparently used be a draft policy but it's gone with Alioth
> now.
> The remnants I could find [5] don't mention package dependencies. Looking at
> the
> archive, I see pretty much uniform dependencies on php-common, apparently
5 matches
Mail list logo
