Closed mp4096 closed 7 years ago
Ugh, musl
support seems to be Tier 2. Ok, then gnu-libc
.
What do you mean with tier 2? ripgrep also provides musl
binaries.
See this overview of supported platforms.
As I understand it, Tier 1 == works out of the box, Tier 2 == will probably work after some googling, Tier 3 == here be dragons.
I wouldn't be so pessimistic about Tier 2 but I'm also ok with gnu-libc since it's pretty stable (compared to libc++).
Update: Especially for a debian package one can expect to have a decent version of libc preinstalled.
I wouldn't be so pessimistic about Tier 2
Sure, I mean we use armv7-unknown-linux-gnueabihf
for the emoji stuff and it works like a charm (after some googling and configuring cargo
). But stuff like i586-pc-windows-msvc
?..
What do you think about 32bit systems?
I don't want to support them. Indentex is by no means a mission-critical piece of software, so hopefully nobody would want to install it on an old 32-bit system.
Should we package a man file?
No, I think indentex --help
+ web documentation should be enough for the first time being. When we have a spec (hoho) and a website (hohoho), we can think about manfiles.
Finally, a working auto packaging and deployment! :sweat:
We have to look into
cargo-deb
.@syxolk Do you think dynamic linking to GNU
libc
is ok? Or should we compile withmusl
?