On Wed 15 Jan 2020 at 11:03:26 +0100, Benny Siegert wrote:
> The developer typically does the following in this case:
>
> 1. Rename the binary (in post-install or something) to
> pylupdate5-${PYVERSION} and install it as such.
> 2. Add an ALTERNATIVES file to link the executable to pylupdate5.
> 3. (and this may be the hardest part) If dependent packages run the
> tool, have them run pylupdate5-${PYVERSION} instead.
Ok, now that I have postponed the firefox problem (I can stay on 69)
with wip/firefox69-2019Q4, I can have a look at doing this.
-Olaf.
--
Olaf 'Rhialto' Seibert -- rhialto at falu dot nl
___ Anyone who is capable of getting themselves made President should on
\X/ no account be allowed to do the job. --Douglas Adams, "THGTTG"
Attachment:
signature.asc
Description: PGP signature