Re: [Python-modules-commits] [python-cpuinfo] 02/02: Import Debian changes 3.0.0-1
are we really suggesting to create a separate binary package, for a
single script, not even 400 bytes (in py-cpuinfo case, but i bet there
are more just like this), mainly boilerplate, that simply loads the
entrypoint from the main module and nothing else? that seems overkill
to me (and probably not only to me, given how much discussion there
was on d-devel about small node packages)
but if you really want to go that road, and avoid clashes, maybe
`<main_module>-cli` would be my suggestion for the bin pkg name
On Sun, Apr 16, 2017 at 2:32 PM, Ondrej Novy <novy@ondrej.org> wrote:
> Hi,
>
> 2017-04-16 18:09 GMT+02:00 Mattia Rizzolo <mattia@debian.org>:
>>
>> Surely I'm not the only one who would consider moving the file back to
>> python3-cpuinfo a step backward…
>
>
> ack. I like solo binary package for /usr/bin/* tools too.
>
> --
> Best regards
> Ondřej Nový
>
> Email: novy@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
>
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
Reply to: