On 27/12/22 3:47 PM, Israel Galadima wrote:
Hi,
I've found that the upstream author for @unicode packages
uses node-unicode-data to generate the unicode data for all @unicode
packages.
I was thinking that we could replace all current and future @unicode
packages with node-unicode-data instead of having separate packages
for them.
The workflow I am proposing is that we pass the unicode version as a
parameter to node-unicode-data and it will download and generate the
unicode data for that version.
Ideally we should be able to get these using watch file/uscan. I'm not
commenting on the suitability of the whole approach (my comment is
limited to getting orig.tar part), lets see if others have any comments.
node-unicode-data is not a published npm package so here is the git repo:
https://github.com/node-unicode/node-unicode-data. @unicode packages
are only used as build dependencies.
I'd be happy to work on the package if the suggestion is agreed upon.
Regards.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
