[Pkg-javascript-devel] must node-* packages depend on nodejs or not?
Pirate Praveen
praveen at onenetbeyond.org
Sun Sep 6 14:12:59 BST 2020
On Sun, Sep 6, 2020 at 15:04, Jonas Smedegaard <dr at jones.dk> wrote:
> Thanks.
>
> I was clearly mistaken: I have now (after reading above CTTE ruling)
> learned that there is _no_ rule in Debian that "Python3 libraries must
> depend on python3" - instead the reason for the required runtime
> dependency is that Python does byte-compilation in a postinst hook.
>
> (I don't know if Perl dependency is cargo cult or what its logic is)
>
> From now on - unless someone stops me and convinces me otherwise - I
> will practice the following, and recommend all in the team to do the
> same:
>
> a) node-* packages _only_ shipping nodejs library code should _not_
> depend on nodejs.
>
Sounds good, may be we should change npm2deb to make it default as well.
> b) node-* packages shipping both nodejs library code and web browser
> library code should _not_ depend on nodejs.
>
agreed.
> c) node-* packages shipping both nodejs library code and a user-facing
> non-essential executable should _recommend_ nodejs.
I don't think we should recommend nodejs as excluding nodejs requires a
conscious choice since installing recommends is default in apt.
Suggests should be sufficient in my opinion.
> d) node-* packages shipping both nodejs library code and a user-facing
> essential executable should ship the executable in a _separate_
> non-library package which depends on the library package and nodejs,
> and
> the node-* package should _not_ depend on nodejs.
I don't think ftp masters will accept that, but your mileage may vary.
More information about the Pkg-javascript-devel
mailing list