📦 An independent package manager that every hacker deserves.

Package Name

presenterm

Package Homepage

https://github.com/mfontanini/presenterm

Software Architecture

x86_64, aarch64_arm

Purpose/Description

It's a terminal slideshow tool.

Additional Information

No response

Check Package Availability

No

Default config file: data="/home/user/.local/share/hysp/data/Architecture/"

Explanation immediately below data Directory to save pkg data ~/.local/share/hysp/data

Noticed because it seemed strange to have a single bin dir for x64 and aarch64 with different data dirs for the two. Probably just a documentation misfire.

Dear @pwnwriter,

First and foremost, I'd like to extend my heartfelt appreciation for your work on this fascinating project. It's been an exciting journey exploring what hysp has to offer.

I've recently encountered a minor issue that I believe could be improved for a better user experience. Upon initial use of hysp, specifically when running hysp list, I received an error message due to the absence of any installed packages. While the error makes sense given that no packages were installed, I propose a more user-friendly approach to this scenario.

Currently, the system responds with the following error:

$ hysp list
Info: Using default configuration.
────────────────────────────────
Error listing files in /home/steinbrueckri/.local/share/hysp/bin: No such file or directory (os error 2)

A more informative and less technical response could enhance the user's understanding of what needs to be done next. For instance, a message like "You have not installed any packages yet" would immediately clarify the situation without implying a system error.

This small change could significantly improve the user experience, especially for those who are new to hysp.

Thank you for considering this suggestion. I am looking forward to your thoughts and the continued evolution of this project.

Best regards, Richard

Bumps serde from 1.0.192 to 1.0.193.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps spinoff from 0.7.0 to 0.8.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

1. Add/Use metadata in config.toml

• Note : This should be an optional feature, toggled only if config.toml contains [source].metadata, else print [source].metadata not defined in config file (for self-hosting people)
• Default config.toml should contain this field as all the backend work is already done

  [source]
  aarch = "Architecture"
  metadata = "https://raw.githubusercontent.com/metis-os/hysp-pkgs/main/data/metadata.toml" 
  remote = "https://raw.githubusercontent.com/metis-os/hysp-pkgs/main/data/"
  
  [local]
  home="/home/user/.local/share/hysp"
  bin="/home/user/.local/share/hysp/bin/" 
  data="/home/user/.local/share/hysp/data/"

• Why ?

1. Implement cli to list all available packages based on metadata.toml

hysp list (-a | --all) --> List all available Packages
# Default: hysp cli to list only installed packages can be changed to something like: 
hysp list (-i | --installed) --> List only Installed Packages

---

2. Implement cli to fuzzy search packages based on metadata.toml

hysp search -p foo --> Should search for *foo*
# Default: hysp cli to install packages should stick to using exact matches
hysp install -p foo --> Should install exactly foo, based on foo.toml

---

2. Allow Installing/Uninstalling multiple packages at once

hysp install -p foo bar xyz --> Should install all three, one after another based on their `.toml` files.
# If it's not too much work, the search cli should also be able to search for multiple packages at once:
hysp search -p foo bar xyz --> Should search & print info for all three, and if fuzzy search is already implemented, then it should cotinue to fuzzy search for all three

#Similarly, the remove cmd should also be able to uninstall multiple packages at once
hysp remove -p foo bar xyz --> Should uninstall all three, one after another based on $BIN/$PKG

1. Check if it's already included in hysp-pkgs:

hysp search -p "$PKG"

#-----------------------------------------------------------------------------#
↣ x86_64
#Total Ported Packages --> metis-os/hysp-pkgs
curl -qfsSL "https://raw.githubusercontent.com/metis-os/hysp-pkgs/main/data/metadata.json" | jq -r '.packages[] | select(.architecture == "x86_64")' | jq -r '.name' | sort -u 
#Detailed: https://github.com/metis-os/hysp-pkgs/blob/main/data/x86_64/README.md
#-----------------------------------------------------------------------------#
↣ aarch64 || arm64
curl -qfsSL "https://raw.githubusercontent.com/metis-os/hysp-pkgs/main/data/metadata.json" | jq -r '.packages[] | select(.architecture == "aarch64_arm64")' | jq -r '.name' | sort -u
#Detailed: https://github.com/metis-os/hysp-pkgs/blob/main/data/aarch64_arm64/README.md

2. Check if it's being built at Azathothas/Toolpacks but not yet ported to hysp-pkgs

Diff:  https://github.com/metis-os/hysp-pkgs/blob/main/.github/PKGS_DIFF.txt

#-----------------------------------------------------------------------------#
↣ x86_64
#Total Hosted pkgs --> Azathothas/Toolpacks
curl -qfsSL "https://api.github.com/repos/Azathothas/Toolpacks/contents/x86_64/" | jq -r '.[].name' | sort -u
#Detailed: https://github.com/Azathothas/Toolpacks/blob/main/x86_64/README.md
#-----------------------------------------------------------------------------#
↣ aarch64 || arm64
#Total Hosted pkgs --> Azathothas/Toolpacks
curl -qfsSL "https://api.github.com/repos/Azathothas/Toolpacks/contents/aarch64_arm64/" | jq -r '.[].name' | sort -u
#Detailed: https://github.com/Azathothas/Toolpacks/blob/main/aarch64_arm64/README.md

• If PKG xyz shows up here, have patience, it will eventually be added to hysp-pkgs
• There's a pinned issue https://github.com/metis-os/hysp-pkgs/issues/1 that tracks this very thing

3. If PKG xyz really doesn't exist

1. Search if it already exists at : https://github.com/metis-os/hysp-pkgs/issues
2. Create an issue at : metis-os/hysp-pkgs
3. Use this template:

Title : [PKG REQUEST] $Package_Name for $AARCH
# Example: [PKG REQUEST] fzf for x86_64 Linux
Body :
- Repo : Include Link to Source Code (Github/Gitlab etc)
- Description : A brief description about the pkg, what it is about/does etc.
- Binary Releases : Whethere pre-compiled binaries are provided, if they are then `Yes` else `No`
   - If Binaries are already provided, download/extract it & include output for `file $PKG` & `ldd $PKG`
   - #Example : https://github.com/metis-os/hysp-pkgs/issues/2
- Needs to compile : If Releases are not provided,, or they are dynamic, write `Yes` else `No`
- Compile Instructions : If $PKG needs to be compiled & you know how to make it static, please include the build description.

• Note: Your PKG xyz must be able to be compiled statically (Usually go/rust) or have their static binaries published as Releases.
• An attempt will be made to compile PKG xyz, but ***if it's always dynamic***, PKG xyz wont be added to hysp-pkgs
• Compiled Binary must be less than 100 MB in size. This is because of Github's Size limit.

Bumps clap from 4.4.8 to 4.4.10.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.