Centralised path management for multi-subpackage projects
uzibalqa <[email protected]>
| Newsgroups | gmane.emacs.help |
|---|---|
| Message-ID | <lkGYC7mX6A9wnHKyN6k2z1KWjUq-WLA5BvUjh-vPJCda2KCac5L5q-DXUh5aGOPIWbb6tMY8MuZwej8vrfT41JVtFg4pKcakZVk3gwBB6IQ=@proton.me> |
Have made an Emacs toolset with multiple subtools, each requiring knowledge of specific directories containing .el files. These paths must be added to `load-path' before calling `require' on the respective libraries. Rather than duplicating path definitions across every subtool with possibility of update difficulties issues and hardcoded user directories, a centralised high-level controller file that defines all paths via defcustom variables would produce a maintainable system. Users could then override paths in one place or via the Custom interface if they place the code locally. What are your thoughts on this? Particularly insights from those who have implemented similar multi-subpackage schemes with shared path management.