4 ms·

Even with the "Why??" section of the readme, I was left wondering "Why?"

by ericyd 3y ago

xpe 3y ago
/me seeing the icon selection: eyebrows raised, head scratched
- croes 3y ago
  For me it's a red flag.
giancarlostoro 3y ago
Sounds like he wants a uniform way to install anything on any Linux OS, default package manager limitations be damned.
- fodkodrasz 3y ago
  But this is already solved by nix or pkgsrc.
  - xpe 3y ago
    I hope we never find a time where a person (whether it be a researcher, tinkerer, dreamer, visionary, misfit, whatever) hears "X is already solved" and says "that's good enough for me".
deleted 3y ago
[deleted]
azathothas 3y ago
Hi, I am the package maintainer for https://github.com/metis-os/hysp-pkgs https://github.com/metis-os/hysp-pkgs (The default source that's shipped with hysp) To address your concerns: 1. Yes, the readme could be better and have better documentation explaining the why. We will update this and clearly list the reasons. Thanks for pointing it out. As to the actual why: 1. Be completely agnostic: Do not depend on or care about what OS, Architecture & dependencies are installed. Just parse config.toml, based on that, install what's needed. 2. The default pkg source that ships with hysp, contains only statically compiled/linked binaries that will work on anything. 3. As installing random binaries from random sources is not advisable due to security concerns, the pkg-source can be self-hosted by anyone and hysp can be configured to use that instead of the default source.
- ericyd 3y ago
  I actually love that you included a "Why" section in your readme, very few projects do that and I think it's extremely useful. So props for that. I think some specific questions that would be nice to address: 1. I would recommend writing out Capture The Flag, CTF may not be as widely known as you imagine (I had to google it). Having unfamiliar jargon at the top of the readme might turn off prospective users who could benefit from your features. 2. How does this compare to some of the alternatives that others have mentioned, and why / how does this solve the problems differently? Of course it's totally great to make software just for fun, but I get the sense this project serves a specific purpose. Good luck to you!

Even with the "Why??" section of the readme, I was left wondering "Why?"

by ericyd 3y ago

Even with the "Why??" section of the readme, I was left wondering "Why?"

xpe 3y ago

/me seeing the icon selection: eyebrows raised, head scratched

croes 3y ago
For me it's a red flag.

giancarlostoro 3y ago

Sounds like he wants a uniform way to install anything on any Linux OS, default package manager limitations be damned.

fodkodrasz 3y ago
But this is already solved by nix or pkgsrc.
- xpe 3y ago
  I hope we never find a time where a person (whether it be a researcher, tinkerer, dreamer, visionary, misfit, whatever) hears "X is already solved" and says "that's good enough for me".

deleted 3y ago

[deleted]

azathothas 3y ago

Hi, I am the package maintainer for https://github.com/metis-os/hysp-pkgs https://github.com/metis-os/hysp-pkgs (The default source that's shipped with hysp) To address your concerns: 1. Yes, the readme could be better and have better documentation explaining the why. We will update this and clearly list the reasons. Thanks for pointing it out. As to the actual why: 1. Be completely agnostic: Do not depend on or care about what OS, Architecture & dependencies are installed. Just parse config.toml, based on that, install what's needed. 2. The default pkg source that ships with hysp, contains only statically compiled/linked binaries that will work on anything. 3. As installing random binaries from random sources is not advisable due to security concerns, the pkg-source can be self-hosted by anyone and hysp can be configured to use that instead of the default source.

ericyd 3y ago
I actually love that you included a "Why" section in your readme, very few projects do that and I think it's extremely useful. So props for that. I think some specific questions that would be nice to address: 1. I would recommend writing out Capture The Flag, CTF may not be as widely known as you imagine (I had to google it). Having unfamiliar jargon at the top of the readme might turn off prospective users who could benefit from your features. 2. How does this compare to some of the alternatives that others have mentioned, and why / how does this solve the problems differently? Of course it's totally great to make software just for fun, but I get the sense this project serves a specific purpose. Good luck to you!