InstallerNG in new AmigaOS 4

[System]

It creates proper uninstall scripts

Really? So if I install two apps, A and B, in this order, and they both want to install the same library (which will naturally only be installed by A, since it already exists when installing B), then will the library be removed if A is uninstalled? Or will it be removed only after both A and B are uninstalled, as it should?

[System]

it shouldn't be too hard to implement - just store a list of all libs etc. installed with a count of the number of apps which appear to use them. If it's greater than 1 at uninstall, leave them. If it's 1 at uninstall, remove them.

I bet this is how M$ would do it, but it's not that simple. It also has to support uninstall cleanups because of inconsistencies made by users who manually "uninstall" programs. It should probably also store what versions of a particular library some application needs and wants. It should also support upgrading existing applications. [...]

[System]

Yeah, but the whole point is that you don't have to do that sort of thing by hand...

I assume you mean manually "uninstalling" programs. (You sound very much like a M$ employee.)
If something can be screwed up some way then there will always be someone that manages to do it. You can never rely on the users to behave. Programs must always take worst-case scenarios into account!

[System]

InstallerNG Homepage

savage@light-speed.de

i was working on the InstallerNG for a long time. it started off as a compiler project, thus i emphasised a clean language specification and a good compiler kernel. it occured pretty early to me that the C= Installers language, as well as its implementation is bretty bad. by doing a better job i had to accept the fact that really bad scripts won't work anymore. but those scripts can be fixed within minutes. compatibility is a big issue, i agree, but i prefer to have a good compiler and bug-fix scripts rather than having a lousy compiler that swallows everything. (btw, its harder to make mistakes if the compiler is picky. accept that!)

some of you complain about the iNG crashing. so send me a bug-report then, and i can try to fix it. i rely on you guys here, since the iNG works on my machine, and many many others do not have a single problem.

future work... well, send me bug-reports. send me suggestions. send me scripts if you think they are right. you want the iNG to be a useful tool? me too... then support it, and don't just complain how $#@! the iNG is.