From: Bill Welch <bill@brazier.com>
To: cygwin@cygwin.com
Subject: Re: How about a 64-bit installer that doesn't require UAC?
Date: Sun, 03 Nov 2013 18:45:00 -0000 [thread overview]
Message-ID: <527699A4.3050806@brazier.com> (raw)
In-Reply-To: <832145579.20131103022843@mtu-net.ru>
I presume you're referring to
http://cygwin.1069669.n5.nabble.com/cannot-run-setup64-exe-without-admin-privileges-even-if-renamed-foo-exe-td102712.html,
where the final (official cygwin, apparently) word is that you think
cygwin users are too stupid to be allowed a choice in 64-bit, that they
have in 32-bit, no matter how locked down and single user their
corporate machine might be.
Thanks.
On 2013-11-02 18:28, Andrey Repin wrote:
> Greetings, Bill Welch!
>
>> Yes, I could try to change the application manifest myself, but that
>> seems esoteric and I haven't been able to find any GPL tool.
> I suggest you use search before posting. This has been discussed already.
> The real solution would be a tool that run in postinstall scripts and can
> prompt user for privilege elevation, but noone had time or inclination to
> write one. Yet.
>
>
> --
> WBR,
> Andrey Repin (anrdaemon@yandex.ru) 03.11.2013, <02:26>
>
> Sorry for my terrible english...
>
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-11-03 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 20:43 Bill Welch
2013-11-02 22:35 ` Andrey Repin
2013-11-02 23:05 ` Andrey Repin
2013-11-03 18:45 ` Bill Welch [this message]
2013-11-03 19:13 ` Bill Welch
2013-11-04 11:53 ` Corinna Vinschen
2013-11-04 15:59 ` Christopher Faylor
2013-11-04 16:11 ` Corinna Vinschen
2013-11-08 14:01 ` Shaddy Baddah
2013-11-08 18:44 ` Denis Excoffier
2013-11-08 19:58 ` Buchbinder, Barry (NIH/NIAID) [E]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527699A4.3050806@brazier.com \
--to=bill@brazier.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).