diff options
| author | Silvio Rhatto <rhatto@riseup.net> | 2023-06-01 15:10:10 -0300 |
|---|---|---|
| committer | Silvio Rhatto <rhatto@riseup.net> | 2023-06-01 15:10:10 -0300 |
| commit | cc61e5fd447cf915b09662568d65c222de9e116f (patch) | |
| tree | 4d967859d974496201fe8f4e5a6366ad19710ccb | |
| parent | 5a844bb11a25443fe00d578f94d8641ff9cbfc61 (diff) | |
| download | trashman-cc61e5fd447cf915b09662568d65c222de9e116f.tar.gz trashman-cc61e5fd447cf915b09662568d65c222de9e116f.tar.bz2 | |
Fix: README: typos
| -rw-r--r-- | README.md | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -29,7 +29,7 @@ by this one: Instead of being just a shorthand, `trashman` packages can try as best as possible not to fetch keys and scripts from remote locations without some basic checks. So if you have to add files into `/etc/apt/trusted.gpg.d`, `trashman` will provide those -keys or fingerprints instead of donwloading it from somewhere, in which case it could +keys or fingerprints instead of downloading it from somewhere, in which case it could be easily tampered. ## Hoarder @@ -60,7 +60,7 @@ locally, at the current user's folder: * Provides basic automation: instead of always running command by hand, recipes can be included in your deployment scripts. -* The one to rule then all; a meta package manager suporting any other +* The one to rule then all; a meta package manager suportting any other package manager, like apt/dpkg, stowpkg, pkg_src, etc. ## Limitations @@ -72,17 +72,17 @@ locally, at the current user's folder: * Do not use your main system for installing `trashman` packages. Use a Virtual Machine instead: this is more manageable and keep the litter isolated from the other parts - of your infostructure. + of your infrastructure. * Not everything can be checked in advance by `trashman` packages. Each package can do it's best to check sources and avoiding running unsigned/untrusted code from remote locations. -* This software is a poor mitigiation and a way to save yourself some time in a growing +* This software is a poor mitigation and a way to save yourself some time in a growing trend of open source software lifecycles dominated by conglomerates running their "cloud" providing you with "open core" applications, taking over your computing stack. -## Instalation +## Installation Simply clone it and add to your `$PATH`: @@ -106,7 +106,7 @@ Syncing the codebase is a two-step procedure. First grab upstream changes: trashman fetch -This will outpupt current OpenPGP signature's from the last commit. You might +This will output current OpenPGP signature's from the last commit. You might check that and also check for repository changes. Once you're fine with those, do the actual merge: |