Daniel Mendler <[email protected]> writes: >> But if we have vendored compat, we can't step into the namespace, or >> packages may load *Org's* compat instead of installed. That will create >> a lot of headache for everyone. > > Yes, the Compat code should not be modified. My point is that the > vendored Compat should only be used for the tests when executing the Org > scripts, with the only goal of ensuring its availability for offline use > as Morgan wanted.
Fair. > But there are certainly other ways to install the git version, via the > git package managers (Elpaca, Straight, package-vc, ...). These package > managers have to make sure to not accidentally install the vendored > Compat. Do these tools blindly install every *.el file, or only files in > the lisp/ directory? If they only install lisp/, then there shouldn't be > a problem if you place the Compat code in vendor/compat/? I think straight only installs from root directory by default and explicitly from lisp/ for Org recipe. So, it should not be a problem. Just like org-test.el is not a problem. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
