On 08/02/2022 17:20, Jonas Smedegaard wrote:
Quoting Yadd (2022-02-08 16:28:22)
Since I saw you prefer to customize component names, I just added a
"-p" option to add-node-component (usable as environment variable:
PKGJS_CMP_PREFIX) to set a prefix to component names generated by
add-node-component. Will be released with pkg-js-tools 0.11.13.
Thanks, I appreciate that.
I must admit, however, that I feel alienated by pkg-js-tools and don't
use those tools, but edit files in the debian subdirectory by hand.
Let's take this "add-node-component" tool as an example...:
I find the name unintuitive, and feel that it pollutes the global
namespace. What I would find intuitive was to type "pkg-js" and hit TAB
to see which tools was available, and if that provided nothing then I
would try "pkg" + TAB in case the tools used some other concatenating
character than dash. pkg-kde-tools is structured like that, and
pkg-perl-tools is structured somewhat like that (it contains one tool
"dpt" arguably confusingly named and a few general-purpose tools).
Even if you told me that a tool exists to add embed components in
packages, how would I find that? It is not mentioned in long
description of the package, so won't show if I search for it with apt,
apt-cache search, axi-cache search, or other similar tools.
I'm not fluent in English, please help me to fix this proposed description:
Package: pkg-js-tools
Provides: dh-sequence-nodejs (= ${binary:Version})
Description: collection of tools to aid packaging Node modules in Debian
The Debian JavaScript Group works on packaging JavaScript libraries for
Debian. This collection contains tools which help the group with
day-to-day work.
.
It provides some utilities:
* debhelper files (set dh-sequence-nodejs into build dependencies) to
automatically:
+ link or copy needed modules into node_modules/ directory
+ launch test
+ choose files to install
+ build "Provides" value for package with components
+ build pkgjs-lock.json and "X-Javascript-Built-Using" value files
for packages built with webpack/browserify
+ clean all its stuff during dh_auto_clean step
* add-node-component: manage uscan components
* github-debian-upstream: creates debian/upstream/metadata for GitHub
source
* debcheck-node-repo: compares vcs repo registered in npm registry
with the source repo declared in debian/watch
* dh-make-node: build debian/ directory in a source repository of a
node module
* pkgjs-audit: a `npm audit` that uses Debian dependencies
* pkgjs-depends: find needed dependencies for a node module
* pkgjs-ln: link a Debian dependency into node_modules/
* pkgjs-ls: a `npm ls` that search also in Debian directories
* pkgjs-utils: various little utilities
.
and also:
* a salsa(1) configuration file for JS Team
* "pkg-js-extra" profile for lintian
--
Pkg-javascript-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
