Script Apt Get

Logs install and upgrade actions for apt-get via script

---

• ⬆️ Top of Document

• 🏗️ Requirements

• ⚡ Quick Start

• 🧰 Usage

• 🗒 Notes

• 📈 Contributing

  • 🔱 Forking
  • 💱 Sponsor

• 📇 Attribution

• ⚖️ Licensing

---

Requirements

Prerequisites and/or dependencies that this project needs to function properly

• Debian derived distribution

• Sudo or Root permissions

---

Quick Start

Clone this project...

mkdir -vp ~/git/hub/paranoid-linux

cd ~/git/hub/paranoid-linux

git clone [email protected]:paranoid-linux/script-apt-get.git

Install via symbolic link...

cd ~/git/hub/paranoid-linux/script-apt-get

sudo ./linked-install.sh

Update in the future with Git...

cd ~/git/hub/paranoid-linux/script-apt-get

git pull origin main

---

Usage

Install a package with apt-get...

sudo script-apt-get install vim

... Above command will generate a log file at a path similar to...

~/Documents/logs/apt-get/install/20200915__vim.script

Or upgrade installed packages with apt-get...

sudo script-apt-get upgrade

... Above command will write a log file to a path similar to...

~/Documents/logs/apt-get/upgrade/20200915.script

---

Notes

This repository may not be feature complete and/or fully functional, Pull Requests that add features or fix bugs are certainly welcomed.

---

To customize where log files are saved set the _log_dir environment variable per command...

_log_dir="${HOME}/script-logs" script-apt-get upgrade

... or via configuration.sh file, eg...

tee -a ~/git/hub/paranoid-linux/script-apt-get/configurations.sh <<'EOF'
_log_dir="${HOME}/script-logs" script-apt-get upgrade
EOF

---

For multi-user systems it is a good idea to clone this project to a root owned directory instead, eg...

cd /usr/local/etc

sudo git clone [email protected]:paranoid-linux/script-apt-get.git

cd script-apt-get

sudo ./linked-install.sh

---

Contributing

Options for contributing to script-apt-get and paranoid-linux

---

Forking

Start making a Fork of this repository to an account that you have write permissions for.

• Add remote for fork URL. The URL syntax is [email protected]:<NAME>/<REPO>.git...

cd ~/git/hub/paranoid-linux/script-apt-get

git remote add fork [email protected]:<NAME>/script-apt-get.git

• Commit your changes and push to your fork, eg. to fix an issue...

cd ~/git/hub/paranoid-linux/script-apt-get


git commit -F- <<'EOF'
:bug: Fixes #42 Issue


**Edits**


- `<SCRIPT-NAME>` script, fixes some bug reported in issue
EOF


git push fork main

Note, the -u option may be used to set fork as the default remote, eg. git push fork main however, this will also default the fork remote for pulling from too! Meaning that pulling updates from origin must be done explicitly, eg. git pull origin main

• Then on GitHub submit a Pull Request through the Web-UI, the URL syntax is https://github.com/<NAME>/<REPO>/pull/new/<BRANCH>

Note; to decrease the chances of your Pull Request needing modifications before being accepted, please check the dot-github repository for detailed contributing guidelines.

---

Sponsor

Thanks for even considering it!

With you may sponsor paranoid-linux on a repeating basis.

Regardless of if you're able to financially support projects such as script-apt-get that paranoid-linux maintains, please consider sharing projects that are useful with others, because one of the goals of maintaining Open Source repositories is to provide value to the community.

---

Attribution

• GitHub -- github-utilities/make-readme

• Unix StackExchange -- How to get the name of the user who executed a bash script as sudo?

---

License

Logs `install` and `upgrade` actions for `apt-get` via `script`
Copyright (C) 2020 S0AndS0

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published
by the Free Software Foundation, version 3 of the License.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License
along with this program.  If not, see <https://www.gnu.org/licenses/>.

For further details review full length version of AGPL-3.0 License.