>=C2=A0 =C2=A0 The same situation is e.g. for python. You can use pip to=
install
>=C2=A0 =C2=A0 packages. And there are python packages provided by distr=
ibutions.
>=C2=A0 =C2=A0 Some people prefer OS packages, some prefer the native pa=
ckage manager.
>=C2=A0 =C2=A0 Not sure what to do about this situation.
It's easy to make a .deb package which installs an Elisp package in the=
way package.el would have installed it (but with global scope).
The two aren't 100% equivalent (upgrading/removing a dpkg-installed
package via package.el won't do the right thing), but the Debian
packages can easily do better than what is there now.
My understanding =
is as follows: to build such a Debian package, you'd have to install th=
e byte-compiled files in a directory with the same name as the Emacs packag=
e, and add its parent to package-directory-list in site-start.d, is that ro=
ughly correct?