I see https://github.com/orbit-online/records.sh as good solution for core logging

Hi @andsens @orbit-online,

I would like to thank you for your tremendous work on open-source projects like Orbit Online. I am grateful that you have recognized BPKG as a package manager.

I'm in the last year work on MUSH another side-project mostly inspired to Rush with the mission to create a Builder tool for large Shell projects.

Please consider if it can have impact on your work, we are open to contributions and supports.

The following projects could be rewritten as Mush package

• https://github.com/drwetter/testssl.sh
• https://github.com/p8952/bocker
• https://github.com/bpkg/bpkg
• https://github.com/nvm-sh/nvm/

For more of them visit https://github.com/awesome-lists/awesome-bash

• Bash validate script before run (Add bash core api that implement integrity check before run or source any script, based on notable integrity external or remote tool)

• https://github.com/wolandark/BASH_Scripts_For_Everyone/blob/main/ssh-port
• https://github.com/kneutron/ansitest

👋 Benvenuto

Grazie tante per il tuo tempo prezioso, eccoti le istruzioni per poterti permettere di non sprecare nenche un minuto

📝 Istruzioni

1. Fai il fork di questo progetto: https://github.com/javanile/mush
2. Fai il fork di questo progetto: https://github.com/francescobianco/mush-packages
3. Crea una issue usando questo link ed incolla dentro i link dei tuoi fork, useremo questa issue per discutere vari dettagli e varie casistiche rilevate nei tuoi test
4. Installa Mush da riga di comando usando la guida seguente: https://mush.javanile.org/
5. Crea nel tuo fork mush-packages un nuovo package all'interno della cartella packages/, prova a creare uno strumento semplice che magari usa un argomento in input al tuo progetto per generare un file con la data nel nome (guarda la sezione seguente "Esempio Pratico")
6. Crea una pull request per aggiungere il tuo nome in questo file: contributors.md
7. Crea una pull request per aggiungere tre idee di package in questo file package-ideas.md
8. Prova a create un package che possa essere utile per te o per le persone con cui collabori o con cui condivi una passione (es. Scacchi, Arduino, Droni, ecc...)
9. Crea nel README.md del tuo progetto mush-packages una lista dei pacchetti che esso contine e per ogniuno indica una descrizione e come e possibile installarlo

🛠️ Esempio Pratico

Creare dentro il proprio mush-packages un progetto chiamato fileshot che semplicemente passatogli il nome di un file esistente nel proprio pc, esso crei una copia di quel file ma aggiunga nel nome un timestamp relativo al momento della chiamata del comando fileshot, in modo da avere qualcosa di simile a questo

$ fileshot mybackup.zip
Snapshot was created with the name: mybackup_202309131200.zip

🎯 Finalità

Tutti questi passaggi hanno lo scopo di farti esplorare il progetto Mush, e di far emergere il tuo punto di vista sulle attività. Nulla qui, è scritto sulla pietra, tutto può essere messo in discussione, sulla base delle esisgenze specifiche che ogniuno ritrova nel proprio quotidiano.

🙏 Grazie

Se hai completato la lista voglio ringraziarti ancora una volta. Molto probabilmente, se ti fa piacere, potrei farlo pubblicamente con un post su tutti i miei social e sul mio blog. Inoltre se dovessi trovarti dalle mie parti, ovviamente sarai ringrazianto con una buona quantita di: Arancine, Cannoli e Olio DOP di altissima qualità.

... it's not clear what this is, from this post, the github repo, or the webstie....

What is meant by a "shell package" ? This is not a standard concept by far, you're going to need to explain what the problem domain is before getting to talk about the solution...

What does this do? Multiple shell scripts combined to one? (it's a shell script linker?) A combination of the binaries a shell script calls? (an environment gatherer for consistent dependencies? how does that even get resolved?)

The only front page example shows compiling main() { echo "Hello world" ; } but neither use-case above would be needed for it.

And it produces a binary? like, an ELF or EXE? How is that related, or even desirable, for shell scripts? Sounds like a horrendous idea... what kind of benefits even come from this?

Safety isn't a feature of shell scripting, convenience is its hallmark. Where does rust fit into this? Is this transpiling shell scripts into rust, and compiling that? why?

We can't see what this project is about. With the current materials, it looks ... like it doesn't itself even know what it is...

The project seems to be very incomplete, and it is still not clear what it aims to achieve. More work on its explanations are needed, as I stated in prior comment. I gave it a try, it doesn't seem to do any linking, just source calling. So the output executables aren't portable.

The idea seems interesting though. The promise of solving cross-environment compatibility and dependency sounds interesting though. But from my experience so far, trying to guarantee identicity of runtime from shell scripting is non-trivial.

The reason we can have guarantees for programming languages is that the dependencies are first-citizens in the language's ecosystem.

Shell scripting relies on arbitrary binaries of various implementation-flavours. grep is not the same grep on two distros. rsync is not the same rsync on different distros. ssh is not the same implementation on different distros. Their default behaviours are not the same across distros.

So making the promise of cross-platform execution.... is a tall order. My take has been: do basic linking/source inclusion into a single file ; normalise the runtime environments across your park, or write highly-portable scripts using common-denominator utility features. Use re-usable code snippets and linking to abstract away flavour-switching.

Bush is the best way to handle testing at the CLI level, it avoid wraps system call into high-level languages like python and php.

Follow this path:

• https://www.linkedin.com/posts/emmanuel-valverde-ramos_bashunit-activity-7210777933878087680-ifJO/?utm_source=share&utm_medium=member_android
• search for bashunit on https://github.com/phpstan/phpstan-src/blob/5d2d56f79fa01538dda02e43cbc8eea05399e28d/.github/workflows/e2e-tests.yml

Recreate this https://github.com/sharkdp/fd as pure shell software

• https://github.com/89luca89/distrobox

Usare questa ricerca per spammare mush

• https://github.com/topics/useful-bash-scripts
• https://github.com/topics/shell-scripts

fare una pull-request qui per presentare mush

• https://github.com/HarshCasper/Rotten-Scripts/tree/master/BASH/Ports_Scan

mettere in relazione mush e questo

• https://github.com/gruntwork-io/bash-commons

presentare mush a questo signore

• https://github.com/techarkit/shell-scripting-tutorial

presentare mush a questo signore

• https://github.com/Mangeshrex/rxfetch/blob/main/rxfetch

spam mush to

• https://github.com/EvanLi/Github-Ranking/blob/master/Top100/Shell.md

spam presentare mush

• https://github.com/ruanyf/simple-bash-scripts

fare cose con questo

• https://github.com/terminalforlife/ShellProjects