On 2024-10-07 18:58:38, Jérémy Lal wrote:
> Le lun. 7 oct. 2024 à 18:27, Antoine Beaupré <anarcat@debian.org> a écrit :
>
>> Hi!
>>
>> I'm part of the golang team (in CC) which is responsible for packaging
>> the Prometheus package, a golang-based monitoring system. Recently,
>> upstream switched from a "classic" HTML-based interface to a rather
>> more... complicated _javascript_ frontend built with React.
>>
>> We've looked at packaging this in Debian (#1083100, also in CC), and
>> quickly got worried about the number of dependencies we'd need to
>> package.
>>
>> Do you have advice on how to move forward on this?
>>
>> I was wondering if there's some magic command we can run to actually get
>> a more solid view on the tasks needed? Like a command that would parse
>> the package.json and report which packages are missing from Debian,
>> which have WNPP bugs, etc...
>>
>> How involved is it to package React stuff?
>>
>> How maintainable is it in the long run in Debian?
>>
>> Thanks for any advice!
>
> Can you give the link to the upstream package.json file that pulls the
> dependencies, thanks.
Of course! I believe it is:
https://github.com/prometheus/prometheus/blob/main/web/ui/mantine-ui/package.json
... which is called from:
https://github.com/prometheus/prometheus/blob/main/web/ui/package.json
i *think* the "react-app/" directory is the older implementation, which
can be disregarded.
Thanks,
I think the proper method will be to mut-bundle as much, and as cleanly, as possible,
with most packages not re-exported to /usr/share/nodejs, because it is just asking for trouble.
There are tools to help in that task, like pkgjs-tools' add-node-component.
It requires some skills. I can help, but I don't have time to do it entirely.
It's going to be difficult to get this into trixie, unless someone works really hard on it right now.
--
We won't have a theory of everything without a theory of consciousness
- David J. Chalmers