On 6/8/21 3:36 AM, Ben Greiner wrote:
Am 07.06.21 um 19:50 schrieb Jason Craig:
On 6/7/2021 11:24, Ben Greiner wrote:
Am 07.06.21 um 12:48 schrieb Simon Lees:
To me this probably makes slightly more sense then d:l:p:pyqt, d:l:p has never contained all our python packages, packages that are mostly bindings of C / C++ libraries have always tended to live with those libraries.
...
* Why do we have d:l:p:aws, d:l:p:azure, d:l:p:mailman, d:l:p:numeric and so on? With your reasoning, their complete content should go to Cloud:Tools, server:mail, science, etc.
Correct me if I'm wrong but these subprojects contain Python applications not, as Simon specifically talked about, Python bindings to C/C++ libraries. Yes you are correct. But I see no resonable argument why applications should go into DEVEL:languages:python:* but bindings should not.
Well in my mind applications generally probably also should not, with the exception of maybe packages that ship both applications and libraries and those libraries are used by a number of other python libraries. Most of the python applications I maintain for example are in multimedia:apps or X11:Enlightenment:Factory because at the end of the day most people care far more about what an application does then which language its written in. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B