While attempting to package Zed Editor, several issues have been
identified that make it unlikely to comply with Debian policy in its
current state:

* Downloading External Binaries
Zed follows a non-standard approach similar to rustup, rbenv, and pyenv,
where it automatically installs developer tools without user consent [1].
While this behavior can be disabled, doing so renders language servers
unusable [2].
Additionally, Zed cannot utilize language servers installed via apt,
making it difficult to integrate with Debian's package management system.

* Language Servers Run with Full System Access
Language servers are executed without sandboxing, giving them
unrestricted access to the system [3]. This poses significant security concerns.

While upstream acknowledges these issues, no concrete resolution has
been implemented yet.
Given the current situation, I believe it is unlikely to meet Debian’s
policy requirements.
That said, I have already set up a scaffolding for packaging in my
Salsa repository, which can be found here:
https://salsa.debian.org/carlo711/zed-editor
I will keep an eye on further upstream developments and update accordingly.

Best,
Carl

References:
[1] https://zed.dev/docs/development/linux
[2] https://github.com/zed-industries/zed/issues/12589
[3] https://github.com/zed-industries/zed/issues/12358

Reply via email to