4 ms·
I'm pretty sure op meant it in an humorous way. I also think it's a weird non-feature. That's certainly the one item of the survey that made me tick.
by nakkiel 14y ago
I'm pretty sure op meant it in an humorous way.
I also think it's a weird non-feature. That's certainly the one item of the survey that made me tick.
- antirez 14y agoThe idea was just to make sure that after a "make" you get some warning if this is not the latest version of Redis. An upgrade is a cost, so maybe to get a warning before deploying may be a good thing after all. Another simpler thing can just be redis-cli --latest to output the latest version of the Redis server.
- primitur 14y agoI think redis-cli --latest is surely the best way. It polls the redis server, tells the user. Then maybe redis-cli --latest update-cli could do the actual update ..
- simonz05 14y agoThis feature exists at distro-level package managers. Why should Redis solve this as well?
- nakkiel 14y agoI don't get it either. As I said, that's a non-feature. In a typical production scenario, you deploy a specific version of Redis and you don't care if it's outdated or not. That's the tested and production-ready version at Company X.
- viraptor 14y agoThe second one would be great. The first one would make the build process depend on having internet connection. It's a very annoying thing if you build your packages in isolation.