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=h9sNLkqLixKh9qxMl/LqUhNWyWJ3bDrWoSRnzzfYoiS
	XaZGHSQ3IFi5K5fRoeEmOgtO38KuVGXde1QAGgzJo4oz6hE/TQWU/x58Z3uYK3MM
	GZ+mVixT0V7pTB1vSXHzO3MyGIbOLCEpUNb9GSEFERlWdpNuzH7RJ37E7RnlYfRA
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51AF6B99.2000006@users.sourceforge.net>
Date: Wed, 05 Jun 2013 11:47:21 -0500
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Attn: Yaakov [Was: Re: cygutils Postinstall Script Errors With Exit Code 128]
References: <CAHiT=DFj=y4PS5d_mj0erWpB-uCieE+KWh3T=J4wnuSOij5hJA@mail.gmail.com> <51A684AA.2060904@cwilson.fastmail.fm> <51A6948B.3000807@users.sourceforge.net> <20130530090831.GK4471@calimero.vinschen.de> <51A7BB7F.3010001@cwilson.fastmail.fm> <20130531083445.GA30659@calimero.vinschen.de>
In-Reply-To: <20130531083445.GA30659@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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.

>>     cygutils-extra (Util): [requires: cygutils]
>>        almost everything else, including documentation and man
>>        pages (even for the exe's in the Base package)

IMO man1 pages should be packaged together with their executables.

>>     cygutils-x11 (X11): [requires: cygutils]
>>        the two desktop files, and the postinstall scripts that
>>        handle them
>>
>> This way, any package that currently requires: cygutils will almost
>> certainly get the tool it is looking for, without having to change
>> its requires line (and besides, if cygutils is in Base you'd get
>> those anyway).
>
> 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.
>
> And additionally you propose the above change to cygutils.  Sounds good
> to me.  Yaakov?

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.


Yaakov


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