Twitter | Pretraživanje | |
Dan Luu
Huh. I guess this is why it was so much work to maintain a working Octopress/Jekyll install back when I used Octopress (speaking as a non-Ruby dev who didn't maintain a Ruby dev environment and relied on system packages as much as possible)?
Reply Retweet Označi sa "sviđa mi se" More
Dan Luu 11. pro
Odgovor korisniku/ci @danluu
I would regularly try to publish a post or even just fix a typo only to find that I had to install a bunch of packages, override environment variables, etc., to get around what were effectively compiler or linker errors (not that people call them that in a dynamic language).
Reply Retweet Označi sa "sviđa mi se"
Dan Luu 11. pro
Odgovor korisniku/ci @danluu
To be clear, unlike that commenter, I appreciate packaging work since it often lets me run binaries with little work on my part (in another thread, quoted OP says distro packagers are useless), but I thought it was interesting to see why using Jekyll was so high overhead for me.
Reply Retweet Označi sa "sviđa mi se"
Jeff Dickey 11. pro
Odgovor korisniku/ci @danluu
Distro updater programs like apt-get should ideally list pkgs modified from upstream original so users are at least aware. Granted, several packages may require more work to install on a given distro than J R User is comfortable doing, but provenance is half of troubleshooting
Reply Retweet Označi sa "sviđa mi se"
Max Math 11. pro
Odgovor korisniku/ci @jeff_dickey @danluu
We got a bunch of weird bug reports that looked as if some important pieces of our software was just missing. Finally discovered that Debian removed it. So we decided to add a warning if said component was missing. Debian packager told us they would just patch it out 🤷‍♀️
Reply Retweet Označi sa "sviđa mi se"