AM

Application Manager (AM)

• Project: https://github.com/ivan-hc/AM

• Bugs/Issues: https://github.com/ivan-hc/AM/issues

• Soar Repo: ivan-hc-am

• Cache: https://huggingface.co/datasets/pkgforge/AMcache

• Soar CI & Repo: https://github.com/pkgforge-community/AM-HF-SYNC

• Metadata: https://meta.pkgforge.dev/external/am/

• Type: AppImages

---

Trust

While we trust the author & lead maintainers of AM, we have doubts about the sources as AM is just a collection of bash scripts that fetch the actual binary from elsewhere & not their own cache since they don't do prebuilds. This is intentional on their own part.

Their effort to prefer offical packages over third party ones are noted. So is also their spooky note they have when a pkg they add didn't have CI. Read: https://github.com/ivan-hc/AM/blob/main/docs/troubleshooting.md#spyware-malware-and-dangerous-software

However, the very nature of run scripts at build/install time, there's a lot of things that can go wrong.

On a scale of 1-10, we had rate this source as 7, Good enough as long as you view the logs and scripts.

---

Add

(Recommended)

#ONLY If you didn't already use it or have your own custom config
soar defconfig --external
soar sync
soar list 'ivan-hc-am'

[ ~/.config/soar/config.toml ]

• Open it in a text editor

#Open the config file using your favourtie editor
#In this example, we will use micro
mkdir -pv "~/.config/soar" &&\
 micro "~/.config/soar/config.toml"

• Add the repo config

[[repositories]]
name = "ivan-hc-am"
url = "https://meta.pkgforge.dev/external/am/x86_64-Linux.json.zstd"

• Sync metadata

soar sync
soar list 'ivan-hc-am'

• Append

mkdir -pv "~/.config/soar" &&\
tee -a "~/.config/soar/config.toml" <<EOF
[[repositories]]
name = "ivan-hc-am"
url = "https://meta.pkgforge.dev/external/am/x86_64-Linux.json.zstd"
EOF

• Sync metadata

soar sync
soar list 'ivan-hc-am'