4 ms·
apt-get also only works extremely well for FOSS releases. If something is closed source (reality check) the developer will need to maintain the a build for each
by zamalek 12y ago
apt-get also only works extremely well for FOSS releases. If something is closed source (reality check) the developer will need to maintain the a build for each distro+release. The user will also need to add that apt repo and click through Linux's warnings about that.
> What a pity they've decided to take a political position rather than a technological one.
Ironically, it's the political (rather: religious) position of Linux that is getting in the way here. If you're not looking through the rosey colored RMS glasses it's very clear that the dev has taken the practical position.
Don't get me wrong, I wish it was different. Linux has amazing potential, but it unrealistically hostile toward these guys. Maybe SteamOS will bring some uniformity to the situation.
- vetinari 12y agoIf you build your binaries against Ubuntu 12.04 (=glibc 2.15 symbols), chances are, that it will be extremely compatible with many distributions for years to come. Just make sure you know, what API you are really linking against. The resulting package can install the repo by itself - i.e. user downloads the package, install it and suddenly, he has repo for updates installed. Google Chrome does it, for example.
- zamalek 12y agoInteresting! I assume you would have to statically link all other libs? Distros often swap out e.g. libfoo for foolib and from my own experience that usually ends up being a rabbit hole of "make."
- vetinari 12y agoYou need to be able to make call, which libraries you are going to link dynamically. LSB libs, X11 and other parts of the infrastructure with staying history are safe, some random foo library is probably not.