[Libreoffice] Fwd: [PATCH] installer::archivefiles - remove external find and chmod forks

Steve Butler <stevenb -AT- kjross.com.au>
Mon, 20 Dec 2010 18:25:43 +1000

Without knowing much about it, I'd assumed that it might have set the "Read
& Execute" permission on the windows file.  Someone could always try
disabling it and see if it all still works (from a clean build?)

Regards
Steve


On 20 December 2010 17:34, Tor Lillqvist <tlillqvist@novell.com> wrote:

Actually, I wonder what the point in "making DLLs executable" on Cygwin is.
Whether the DLLs in quesiton seem to be "executable" from Cygwin's point of
view (i.e. whether the emulated imaginary POSIX "mode" of the files have the
x bits on or not) is totally irrelevant. Probably that part of the Perl code
could be dropped completely.

But I would love to be proved wrong, of course... Experimentation needed.

--tml



-- 
Regards,
Steve Butler



-- 
Regards,
Steve Butler

Context

[Libreoffice] [PATCH] installer::archivefiles - remove external find and chmod forks · Steve Butler
- Re: [Libreoffice] [PATCH] installer::archivefiles - remove external find and chmod forks · Tor Lillqvist
  - (message not available)
    - [Libreoffice] Fwd: [PATCH] installer::archivefiles - remove external find and chmod forks · Steve Butler
  - (message not available)
    - (message not available)
      - Re: [Libreoffice] [PATCH] installer::archivefiles - remove external find and chmod forks · Steve Butler

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.