Arch Linux User Repository

In accordance with Python package naming rules, please change pkgname to termux-language-server in PKGBUILD, and resubmit under that name to AUR. Thank you.

Please kindly stop using python- name prefixes for language servers that are not for the Python language itself.

I have already linked the relevant Arch package naming rule for Python in my comment on the python-pkgbuild-language-server page.

Based on that, it is not just a preference of mine or of others, but an actual requirement for all Arch and AUR maintainers to adhere to.

My recommendation does not apply to cases like with python-requirements-language-server, of course.

As the package above is necessarily for Python's requirements listings and not for any other language's dependency definitions.

Please see excerpt from Arch wiki's Python package guidelines:

Package naming

For Python 3 library modules, use python-modulename. Also use the prefix if the package provides a program that is strongly coupled to the Python ecosystem (e.g. pip or tox). For other applications, use only the program name.

In Arch repo, none of the language servers that are implemented in a different language than what language they provide the server for have a name prefix for the implementing language:

https://archlinux.org/packages/?q=language-server

Most of them are made in nodejs or typescript.

This one is made in Python:

• jedi-language-server

And on AUR, these are made in or with Python:

• cmake-language-server
• fortran-language-server
• glsl-language-server (mostly written in C++ but has some Python code as well)

As a developer myself, I don't care which programming language implements a language server, as long as it works and serves its purpose.

But it is confusing to see python- prefix or nodejs- prefix for language servers for autoconf, pkgbuild, dockerfile, sql etc.

Imagine the following packages - aren't these names totally misleading when you see them?

• go-arduino-language-server (Arduino LSP)
• java-groovy-language-server-git (Groovy LSP)
• java-xml-language-server-git (XML LSP)
• nodejs-bash-language-server (Bash LSP)
• python-cmake-language-server (CMake LSP)
• typescript-java-gradle-language-server (Gradle LSP)
• cpp-python-glsl-language-server (okay, deliberately extreme example for GLSL LSP)

:)

Hi,

At least please don't continue to create new language server packages with the python- prefix.

python- packages in general are intended for other Python packages to use.

A language server is intended for any kind of application to use as a plugin.

@MarsSeed, I am not sure, I have many python-XXX-language-servers. If it must be renamed, I need to change all of them. I want to know if more people want it?

Would you resubmit this package under the pkgbuild-language-server name, please?

Hi,

I am very thankful to you for creating this language server.

I would like to suggest to you, though, that you remove the python- prefix from the name.

Many language servers are Python-based, but they don't have this prefix in their package name. The prefix just makes the name a bit more confusing.

Also, Arch only mandates python- prefix for Python libraries that are to be used as dependencies by other Python libraries or applications.

But a language server is a technology-independent plugin for the consuming application. So no need for the prefix as per Arch guidelines.