3 ms·
another suggestion is to start shipping binaries. i just looked at your download page and while it's not much of an issue for me to compile it, it may be just
by there 17y ago
another suggestion is to start shipping binaries. i just looked at your download page and while it's not much of an issue for me to compile it, it may be just enough work to make other people not want to try it. especially when you start talking about header files and dependency versions.
make deb and rpm packages, get it into the freebsd/openbsd/pkgsrc/fink port trees. make your installation page as short as "pkg_add tarsnap" and only link to the compilation instructions for other, less commonly used architectures. (do you have the ability to see what os/arch most of your users are using?)
- cperciva 17y agoBinaries are on my to-do list. I could build a bunch of binaries and put them on the website right now, but I want to have a scriptable build process before I commit to providing binaries. FWIW, Tarsnap is in the FreeBSD ports tree already, but not in others.
- rw 17y agoExplore dual-licensing options for the daemon, too. Tarsnap is the kind of thing that could become a ubiquitous sysadmin tool, if done right!
- ericd 17y agoI would say this is a big one. I'm capable of compiling it myself, but honestly, for trying something out that's not very high on my to do list (since I have a workable solution of my own), the barrier to trial needs to be very low.