[Buildroot] [PATCH v3 1/1] jsen: new package

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Hello,

On Mon, 28 Mar 2016 16:01:09 +0200, J?rg Krause wrote:

> Unfortunatly, scanpypi does not work with latest Buildroot.

Ah. It would be great if some of our Python contributors could take
scanpipy, finish it and send it for merging.

> But I
> tested scancpan and yes, I would say that we need something like this
> for Node.js and npm. However, the problem with dependencies of
> different versions is still there. For example Code-TidyAll depends on
> Moo whatever version. scanspan fetches latest Moo version 2.* and
> creates a fine buildroot package. The perl package Tropo however
> depends on Moo 1.*. Installing this package with scanspac afterwards
> does not change Moo, which is correct I think. However, building Tropo
> will use the package Moo 2.*, which might fail (I've not tested).

This version-dependency thing is indeed a problem. For the specific
case you point out, the solution would be to have separate moo1 and
moo2 packages, very much like we do for python/python3, qt/qt5, etc.

However, this is only realistic if there are only a few "major"
versions for a few packages. If they break the API at every minor
release, then it's clearly not doable.

I personally don't really care about npm/node.js. Maybe we should just
add a big fat legal warning in our legal information when NPM has been
used to install additional packages, to explicitly say that those
additions are not listed in the legal info output. This would at least
warn the user.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com