X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=lnA38QNJKOwzPJ9Vcs0lMDOzvWtwhibHdlbeGUJk127
	MDVLemTnYKLQ+/O9p2jlm/7KWTa2LwenjzFLpmrqsFprOe/WNzceJXuqOviIZ2UH
	U+Cdus3NPqKmhZc+0DdB9SQdbvpimH0czPG1tFUWiN9WEZublIt5aZ2SHe/L6ibA
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=BOFXNNKiNG7Jxvxm5E7XaKc5aVs=; b=byQIn0hNyja4DxRHA
	XzJq5xIcytauAAWC10tgN5FFBhSN5lqi/rqbjtrDAeUTzR2WnjiHiQsOcPED51iv
	Bg9WN1+UArK18kC5fTXVJNcog6/2UcJaHkl3Vt0xYnxnXDHxzEnck2aUcz0me2SO
	gfOpNTjbsE9FPEA33LQZupVFKo=
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
X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,SPF_PASS,TW_NL autolearn=ham version=3.3.1
Message-ID: <51B0A7FE.3080509@cwilson.fastmail.fm>
Date: Thu, 06 Jun 2013 11:17:18 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject: Re: Attn: Yaakov [Was: Re: cygutils Postinstall Script Errors With Exit Code 128]
References: <CAHiT=DFj=y4PS5d_mj0erWpB-uCieE+KWh3T=J4wnuSOij5hJA AT mail DOT gmail DOT com> <51A684AA DOT 2060904 AT cwilson DOT fastmail DOT fm> <51A6948B DOT 3000807 AT users DOT sourceforge DOT net> <20130530090831 DOT GK4471 AT calimero DOT vinschen DOT de> <51A7BB7F DOT 3010001 AT cwilson DOT fastmail DOT fm> <20130531083445 DOT GA30659 AT calimero DOT vinschen DOT de> <51AF6B99 DOT 2000006 AT users DOT sourceforge DOT net>
In-Reply-To: <51AF6B99.2000006@users.sourceforge.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 6/5/2013 12:47 PM, Yaakov (Cygwin/X) wrote:
> On 2013-05-31 03:34, Corinna Vinschen wrote:
>> On May 30 16:50, Charles Wilson wrote:
>>> If we want to include (some subset of) cygutils explicitly in Base,
>>> I could see splitting into three subpackages:
>>>     cygutils (Base):
>>>        cygdrop cygstart lpr mkshortcut readshortcut winln
>>
>> What about "cygstart mkshortcut readshortcut"?  These may be used by
>> postinstall scripts, the other stuff is extra, afaics.
>
> Agreed.

Ack.

> IMO man1 pages should be packaged together with their executables.

Ack.

>> So, as result, we should do this for a start:
>>
>> - cygwin-doc drops "Base" from the categories.
>> - dos2unix adds "Base" to the categories.
>> - cygutils drops "dos2unix" from requires.

Yes.

> The man3 and info pages definitely don't need to be in Base, but it
> would be nice if the man1 pages were packaged with cygwin.  Is that
> possible?  Otherwise, this sounds good to me.

Sure, I can do that. I'll roll a new release tonight (for both 32- and 64-).

--
Chuck



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