![]() ) and is therefore the preferred choice but for system administrators wo want to automatically deploy Inkscape on multiple machines the. exe installer has more features (localization, automatic uninstall of the old version when updating, proper components selections, smaller size. We currently offer two installers, as the. I can't think of any other software I use which has this issue. In fact it turned out I had two earlier versions installed - probably as a result of using different installer types at different times. so I tried MSI, ran it, it showed a message saying an earlier version was installed and I had to remove that first. Wording could be clarified.)īut I didn't remember which installer I used last time (why would I?). (The first statement seems absolute, until you read the next one. "Installers will take care of this automatically, unless you switch the type of installer (e.g. "Please note: Always remove the previous version before updating!" ![]() ![]() org/en/ release/ 0.92.3/ windows/ 64-bit/ I saw these messages: I noticed that an Inkscape update was available (0.92.3) and went to download the 64 bit Windows package. If it is necessary to offer both, they should inter-operate better without causing any confusion to the user. The package can do whatever it wants during its pre- and post-installation hooks, can name and usually find its own dependencies, and leaves a record of its installation in a central location for ease of maintenance.TLDR: Why are both EXE and MSI installers offered? This just seems to be confusing. deb is sort of in between an MSI installer and a setup.exe. deb packages, missing a dependency will just cause a failure to install. Several comments note that MSIs can name dependencies, but since there is no central database of MSIs like there is for. As far as I know, in the Windows world an MSI cannot cause the installation of another MSI, so setup.exe is typically used for this kind of dependency tracking. deb specifies its dependencies, so proper installation can be guaranteed. Since this method does not add the package to the database of installed programs, removing it later can be much more difficult.Īnother difference is that a. configure & make & sudo make install, or whatever other method the authors decided to use. This script is executed in one of these hooks.Ĭloser to setup.exe might be downloading a progam's source code from the project's homepage, then running. The ttf-mscorefonts package is interesting in that the package itself contains only a script to download and install the fonts. deb package then produces entries in a central database of installed packages for ease of maintenance. deb package - the database is locked during installation, so this can only be achieved through dependencies. One thing they can't do is install another. The hooks can effectively do anything on the system, including something I don't think I've ever seen on Windows: adding users for a system service. ![]() deb package includes a tree of files to copy into the filesystem, as well as a collection of pre- and post-installation hooks to run (among other things). Probably closer to an MSI installer than a setup.exe, a.
0 Comments
Leave a Reply. |