I made a small script on my machine and aliasin .bashrcwhich it calls it. This is a 3-line bash script, but it can grow.
Now some people on my team find this useful and want to use it.
Instead of saying "copy this alias, do it, do it, install this lib". I was thinking of creating a simple package to be a little more professional. The fact is, I've never done anything like this before. And the problem for me is not creating a package, it is trying to solve what you usually put in a package.
Suppose I want to take a script and create myapplication. I want to create a .deb file that my command will install, and:
- Is there
/usr/bin/myapplicationor /usr/sbin/myapplication(what is the difference between them?), So they just call myapplicationon their terminal and will work; - Create a help page ; (Where are the man pages in the Debian system usually?);
- You have the opportunity to read
.myapplicationrcin the home folder with some configurations; - You have an entry for shortcuts in your gnome installation (is it possible to have a universal shortcut "format", which is also available for KDE and Gnome?);
- Install the dependencies.
. alias bashrc. . , , ?