Module Creation: Best Practices
Posted: 05 Jun 2016, 21:17
Hi all,
I have been experimenting with Linux via Porteus for a while now given that I use it for web development. This means that I have installed a bunch of tools on it, from editors such as Atom and Sublime Text 3 to browsers like Vivaldi and Firefox to package managers like npm, nvm and such.
The problem is that none of these are modules. I could easily turn their containing directories into modules. But given that I also create symbolic links into /bin or /usr/bin and add executables to PATH, I don't know how to include those in my modules so they are removed / injected as the module is (des)activated.
It would be great if someone could update the module creation tutorials to reflect those use cases. Or just show me how to effectively create modules that have CLI commands, start menu items, etc.
Thanks.
I have been experimenting with Linux via Porteus for a while now given that I use it for web development. This means that I have installed a bunch of tools on it, from editors such as Atom and Sublime Text 3 to browsers like Vivaldi and Firefox to package managers like npm, nvm and such.
The problem is that none of these are modules. I could easily turn their containing directories into modules. But given that I also create symbolic links into /bin or /usr/bin and add executables to PATH, I don't know how to include those in my modules so they are removed / injected as the module is (des)activated.
It would be great if someone could update the module creation tutorials to reflect those use cases. Or just show me how to effectively create modules that have CLI commands, start menu items, etc.
Thanks.