[NSIS-Bugs] [ nsis-Feature Requests-679395 ] 'SetOverwrite ask' option

[SourceForge.net <no...@so...>]

Feature Requests item #679395, was opened at 2003-02-03 12:04
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373088&aid=679395&group_id=22049

Category: Scripting
Group: Version 2.x
Status: Open
Priority: 5
Submitted By: George Stephanov (myxare)
Assigned to: Amir Szekely (kichik)
Summary: 'SetOverwrite ask' option

Initial Comment:
I recently needed a to have my installation ask the
user whether to overwrite file if it already exists. I
easily implemented a new version of SetOverwrite which
when set asks the user whether to overwrite the file if
it already exists.

If somebody else is interested in this feature too it
would be good to be added to the official tree.

----------------------------------------------------------------------

>Comment By: Amir Szekely (kichik)
Date: 2003-03-26 23:07

Message:
Logged In: YES 
user_id=584402

Rename user.config user.config.backup
File /r build\*.*
IfFileExists user.config.backup 0 +3
  Delete user.config
  Rename user.config.backup user.config

----------------------------------------------------------------------

Comment By: Gábor Lipták (gliptak)
Date: 2003-03-26 22:59

Message:
Logged In: YES 
user_id=79346

one would have hoped the 

file
wildcard  

or

wildcard
file

presents the desired result ...

When you are talking about copying would that happen from
within the nsi script?

or the other solution could be:

SetOverWrite off
File build_keep\user.config
SetOverwrite ifnewer
File /r build\*.*

?

----------------------------------------------------------------------

Comment By: Amir Szekely (kichik)
Date: 2003-03-26 22:09

Message:
Logged In: YES 
user_id=584402

If you don't want to specify the files that build\*.* includes one 
by one you should copy user.config to a temporary location, 
copy all of the files and copy user.config back. If user.config 
was already there it won't be overwritten eventually and if it 
wasn't then the new file will remain.

----------------------------------------------------------------------

Comment By: Gábor Lipták (gliptak)
Date: 2003-03-26 21:26

Message:
Logged In: YES 
user_id=79346

thanks for pointer very useful, but i'm not sure I
understand the correct syntax to be used. I would like to
see the following setup:

SetOverWrite off
File build\user.config
SetOverwrite ifnewer
File /r build\*.*

but it seems that user.profile is always overwritten when
build\user.config is touched (as per the rule ifnewer)?

----------------------------------------------------------------------

Comment By: Amir Szekely (kichik)
Date: 2003-03-25 22:06

Message:
Logged In: YES 
user_id=584402

It's actually a per file setting so you can set a different value 
for each file. For example:

SetOverwrite off
File bla # won't be overwritten
File blue # ditto
SetOverwrite on
File foo # will be overwritten
File bar # ditto

----------------------------------------------------------------------

Comment By: Gábor Lipták (gliptak)
Date: 2003-03-25 22:00

Message:
Logged In: YES 
user_id=79346

i maybe mistaken but it seems that this option applies to
all files in the install. and e.g. a newly prepared
executable needs to be updated, while one would want to
leave certain files alone.

----------------------------------------------------------------------

Comment By: Amir Szekely (kichik)
Date: 2003-03-25 17:14

Message:
Logged In: YES 
user_id=584402

What's wrong with using SetOverwrite off before extracting 
the file? The file will never be overwritten but the first install 
will always create it.

----------------------------------------------------------------------

Comment By: Gábor Lipták (gliptak)
Date: 2003-03-25 04:25

Message:
Logged In: YES 
user_id=79346

The capability to support "user configuration" files (which
are provided to the user as a template during first install,
but are not modified during subsequent installs or not
modified if the user already made changes to them) also
would be a welcome addition.

SetOverwrite in the current implementation does not seem to
cover this.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-02-14 12:19

Message:
Logged In: NO 

I agree that "ask" would be useful. If i were implementing it, 
I'd have a "Yes to all" button in the dialog box that 
answered "Yes" until the next SetOverwrite command - so 
you could call SetOverwrite ask again to reset the flag after a 
group of files. 

If SetOverwrite had a "ifnewerversion" option that checked the 
file's version property and not just the date last modified, 
that'd be even better.

bcu...@ar...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373088&aid=679395&group_id=22049