On Fri, 18 Oct 2024 at 15:31:26 +0200, Guillem Jover wrote:
> I guess whether "upstream name or python-$modulename" would seem fine,
> depends on what "upstream name" is. I guess if the latter is something
> like "py<something>" or some widely known sub-ecosystem that is
> really very much python-specific, and there is no chance of that ever
> being present in other language ecosystems (which ahem), then I guess
> that could be fine
src:dbus-python, src:tap.py and src:pygobject seem like some examples of
upstream names that are fine (not going to conflict with other ecosystems)
despite not fitting the /^python-/ pattern.
But, looking at some packages that I happen to have installed, I think
I agree with Guillem that names like src:alabaster and src:binaryornot
seem too generic to be ideal.
smcv
