www.delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
Date: | Wed, 28 Mar 2007 00:48:24 +0200 (MET DST) |
From: | Angelo Graziosi <Angelo DOT Graziosi AT roma1 DOT infn DOT it> |
To: | cygwin AT cygwin DOT com |
Subject: | Files getting 'x' permission installing packages in Cygwin |
Message-ID: | <Pine.OSF.4.21.0703280032040.6167-100000@ax0rm1.roma1.infn.it> |
MIME-Version: | 1.0 |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Just a curiosity. Is it 'normal' that, when one installs packages, files, like *.a, *.h, *.README etc. (i.e. files that normally are not executables), acquires the 'x' permission ? In the tar ball of the corresponding packages they do not have 'x'! Could this have to do with 'setup.exe' (I am using 2.558 snapshot) ? Thanks, Angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |