----- Original Message ----- From: "Lapo Luchini" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 08, 2002 2:16 AM Subject: Re: setup.exe and replacing of in-use files
> >Oh, and BTW: the patch was about 2 minutes work :}. Doing transactional > >installs will be somewhat more :}. > > > I guess with transactional install you mean something like returning to > the package list with the not-correctly-installed packages marked as > "install" or "reinstall" be ok, it that case? I mean turning a single remove|replace|install (of a set of packages) into a transaction - that is it either completes successfully or it gets rolled back so that nothing has changed. Currently if something fails partway through a replace operation, then the software is left broken. > Another option would be to keep yelling a dialog at the used telling > which file is occupied until the file is no longer occupied (again, this > ONLY when setup.exe is launched with the option). Urk. Well it's possible I guess, but seriously annoying for the user. Frankly I don't see the benefit. > BTW: I don't know if it's KDE's setup.ini faults but every time I launch > setup.exe it proposes to me tu upgrade kde-base package from version > 2-2.2.2-b1 to actual version 2.2.2-b1. > And if I select "keep" and then launch install again I get the proposal > to upgrade from 2-2.2.2-b1 to actual version 2.2.2-b1. > And if I select "keep" and then launch install again I get the proposal > to upgrade from 2-2-2.2.2-b1 to actual version 2.2.2-b1. > You got the idea, I guess. The package release field must be pure numeric. I.e. 2.2.2-1, not 2.2.2-b1. If you want a beta tag on packages then try 2.2.2b-1. The package release field provides no information about package status, just versioning. Use the package version field to provide such information. Rob
