X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 18 Dec 2008 09:42:48 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Setup.exe (v2.609) Primary Group Problem
Message-ID:	<20081218084248.GV6830@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<49402BC3 DOT 7050800 AT hotmail DOT com> <4948F8F6 DOT 6040004 AT hotmail DOT com> <20081217134729 DOT GO6830 AT calimero DOT vinschen DOT de> <49494E93 DOT 4080601 AT hotmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<49494E93.4080601@hotmail.com>
User-Agent:	Mutt/1.5.16 (2007-06-09)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Dec 17 14:10, Matt Rice wrote:
> Corinna Vinschen wrote:
>>> Sorry for mailing twice, I never got a response.  Is there a workaround 
>>> for getting the default install group to be what I want it to be?
>> I don't understand why a later chgrp doesn't provide what you need.
>> Corinna
>
> That's what I'm doing now, but that means I have to chgrp every time 
> packages are installed or updated.  One package isn't really a problem, but 
> doing this for many packages is.  I have to know all file paths associated 
> with every installed/updated package and chgrp( -R) on all of them (which 
> can be time consuming).  Even using -R sometimes won't do because some 
> subdirectories' groups would need to remain.
>
> Would adding cmd line arguments for user/group to setup.exe be possible?

http://cygwin.com/acronyms/$PTC
http://cygwin.com/acronyms/$SHTDI

Alternatively, if you have no Cygwin process running, and you don't
have to update the cygwin package itself, you can try running ash
(which probably won't get any updates anyway) and start setup.exe
from there.  The idea is that setup inherits the user token with your
new primary group if started from a Cygwin process.  Only the ash and
cygwin packages can't be updated that way.  But that's just a thought.
I give no guarantee that it works.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/

- Raw text -