From: Leif W <war...@us...> - 2005-08-26 15:18:29
|
> From: "Dave Murphy" <win...@nt...> > Sent: 2005 August 26 Friday 05:32 > Here's my first cut at an NSIS based installer. Thanks for posting! Taking a look, if I understand anything. :p > On first install this app will allow the user to pick a sourceforge > mirror site and request download only or download and install. The Is it possible to code a unique random algorithm in NSIS? With mirrors a b c d, pick b at random, then pick from a c d at random, test if the file exists on the server with a HEAD request, and get it if it exists, or else pick another server, until run out, and then start again with all servers. The point of mirrors is not to overload any single mirror by downloading everything from it. Then maybe a mirror is slow or has some problem, it might be handy to add/remove sources (mirrors). > second dialogue gives a choice of Previous, Current and Candidate Again, this sometimes does not work. It may be the case that the "Current" version does not exist, it's only in "Candidate". But if you choose "Candidate", you don't get what's in "Current". Picking "most recent" should look for the most recent version in any release category. > then extracted to the chosen install directory. Subsequent runs of the > application enter update mode where the user can choose to install > packages not installed on the first run or update installed packages > with newer versions. The installer/updater is copied to the install Ahh, this might suffice, but might be confusing. We'd just have to see what happens. > mingw website. A package maintainer would merely have to upload a new > tarball and edit the appropriate line in the hosted ini file. That might not be too bad. Maybe even scriptable to pull the data, if people stuck the data in a pullable location. > For what it's worth the plugin used to extract the tarballs can also > handle bzip2 and lzma compressed tarballs, both of which would reduce > the size of the downloads. Sweet. As I noticed ealier in the week. > Obviously there's still a little tidying to be done ( license screen > for > one and detection of Windows version for purposes of path inserion) > but > I think this is pretty close to what's needed. Hmm, there's the lacking versioning, dendency or conflict stuff in the .ini. Can NSIS do numerical comparisons and such? I imagine so, but don't know how it'd be specified. I'll read up on NSIS today. Leif |