Ticket #955 (new enhancement)
Installer should fetch its idea of supported releases from the network
| Reported by: | jdreed | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | The Distant Future |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: |
Description
install-debathena.sh should fetch its idea of supported releases from the network, so we can do clever things like support testing releases with disclaimers, etc. See also #925.
Change History
comment:1 Changed 13 years ago by jdreed
- Priority changed from normal to low
- Milestone changed from Natty Release to The Distant Future
comment:2 Changed 13 years ago by geofft
This was found a bit questionable on zephyr. Evan said:
Is there really a reason not to just do that by...changing the installer? If people aren't downloading the latest version of the installer whenever they do an install, they're doin' it wrong. Maybe a better change would be to add a self-updating mechanism to the installer or something?
I replied in agreement with:
If you really want to, insert a date from the server via SSI or some CGI or so, and have the installer say "This installer is more than two days old. Please make sure you have downloaded the latest version. Continue [y/N]?" (with special-casing for the un-SSI'd version, where it prints "Warning: using installer from source repository. This may not be the supported installer.")
Mostly I'm curious if the network info is going to pass through the usual beta/deployment testing process, and what about that process will differ from the current installer.
