Le 02/05/2020 à 12:39, Niels Thykier a écrit :
> Niels Thykier:
>> Control: tags -1 moreinfo
>>
>
> Hi Xavier,
>
> I am still waiting for input from you on the mail below.
>
>> Xavier Guimard:
>>> Package: debhelper
>>> Version: 12.9
>>> Severity: wishlist
>>>
>>> Hi,
>>>
>>> I'm maintaining pkg-js-tools which provides a nodejs-module
>>> auto-installer. I'd like to automatically `chmod +x` files declared as
>>> "bin" in package.json.
>>> * I don't want to automatically install them to /usr/bin because:
>>> * `require` command is related to current directory, then nodejs
>>> binaries must be installed in nodejs dirs and linked to /usr/bin
>>> * I don't want to automatically link them all to /usr/bin since this
>>> will change packages during rebuild and can create conflicts (same
>>> binary names)
>>> * I don't want to "remove_command" dh_fixperms since it is not safe
>>> * I don't want to "insert_after" dh_fixperms since it will be launched
>>> even if maintainer sets a "overrides_dh_fixperms'
>>>
>>> For now, maintainers are using "override_dh_fixperms" but I think we can
>>> use more automatization. Is it possible to write a dh_auto_fixperms
>>> target or giving values using environment variables ?
>>>
>>> Cheers,
>>> Xavier
>>>
>>> NB: sorry for my poor English, tell me if my query is not clear ;-)
>>>
>>
>> Would it be solved by dh_fixperms leaving the exec bit alone in some
>> directory and rely on pkg-js-tools's auto-installer to set that correctly?
>>
>> If not, is there a trivial way to determine which file should have exec
>> bit and which should not (as a "new" general rule to replace #953638)?
>> Or will this require nodejs knowledge (like parsing an upstream file)?
Hi,
sorry for the delay (I lost previous message). Generally Node.js
binaries can be found in package.json ("bin" field). Usually they are in
/node/path/foo/bin where node-path is one of:
* /usr/share/nodejs
* /usr/lib/<gnu-arch>/nodejs
* /usr/lib/nodejs (deprecated)
But it's not always so...
Cheers,
Xavier
