Daniele Scasciafratte
Daniele Scasciafratte
No I checked the issues was happening also before that PR. Probably the PR that added the documentation generator had that issue too. @Ph0enixKM this is for you
I think so, but also there is the issue that printed the whole comments in the file not just the one involved in the function so there is a bug...
So as Debian user I can say that we just need the same binary we compile with cargo has doesn't have any dependence on something else so it should work...
Indeed we can think about crete our own repository in the future. I am more right now on step 1, do the packages.
Just for documentation sake, when we will have the deb package I can host the debian repository on my server. A tool to help with that https://github.com/aptly-dev/aptly
I did a PR for the deb package in the meantime, we provide packages for Nix so why not also for debian based distro?
So the debian support it's in the CI for the next release and probably I will do a debian repository on my personal server. Anyway I am closing it as...
Now is just: ``` In ./date_compare.ab.sh line 11: echo $? ^-- SC2319 (warning): This $? refers to a condition, not a command. Assign to a variable to avoid it being...
I agree we have also other tasks about releases, ideally when it is time for a new release in this other repo we just create a new release and a...
On https://github.com/Ph0enixKM/Amber/pull/185 I added `is_root` and `is_command` that I think that should be built-in commands. The second one just check if a command exists.