Issue 111232 - solenv: temporary progs run by mhids.pl cause UAC dialog
Summary: solenv: temporary progs run by mhids.pl cause UAC dialog
Status: CONFIRMED
Alias: None
Product: Build Tools
Classification: Code
Component: solenv (show other issues)
Version: OOO320m15
Hardware: Unknown Windows Vista
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-28 15:55 UTC by tml
Modified: 2017-05-20 11:27 UTC (History)
1 user (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description tml 2010-04-28 15:55:46 UTC
When generating .hid files from .src files, the script solenv/bin/mhids.pl
creates and runs a temporary program. The name of the program is constructed
from the basename of the .src file. Some .src files have names with strings
"setup", "patch", "update" or "install" in them (one even has two of them...).

Running programs with names that contain these strings (and other similar?)
cause an UAC dialog on Windows Vista and newer. That should be avoided, because
the pointless dialog pauses the build.

There is already a commented-out line in mhids.pl to handle this for "setup",
that needs to be uncommented, and additionally also the other magic strings handled.

Patch:

--- solenv/bin/mhids.pl
+++ solenv/bin/mhids.pl
@@ -151,7 +151,11 @@
 $filebase =~ s/.*[\\\/]//;
 $filebase =~ s/\..*?$//;
 $workfile = "$tmpdir/${filebase}_".$$;
-#$workfile =~ s/setup/set_up/;
+# Avoid UAC prompts on Windows
+$workfile =~ s/setup/set_up/;
+$workfile =~ s/patch/pat_ch/;
+$workfile =~ s/update/up_date/;
+$workfile =~ s/install/in_stall/;
 
 # now get $workfile ready for shell usage...
 $shell_workfile = $workfile;
Comment 1 Rob Weir 2013-03-11 15:01:12 UTC
I'm adding this comment to all open issues with Issue Type == PATCH.  We have 220 such issues, many of them quite old.  I apologize for that.  

We need your help in prioritizing which patches should be integrated into our next release, Apache OpenOffice 4.0.

If you have submitted a patch and think it is applicable for AOO 4.0, please respond with a comment to let us know.

On the other hand, if the patch is no longer relevant, please let us know that as well.

If you have any general questions or want to discuss this further, please send a note to our dev mailing list:  dev@openoffice.apache.org

Thanks!

-Rob
Comment 2 Marcus 2017-05-20 11:27:51 UTC
Reset assigne to the default "issues@openoffice.apache.org".