This is the mail archive of the
mailing list for the Cygwin project.
Re: Attn: Yaakov [Was: Re: cygutils Postinstall Script Errors With Exit Code 128]
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Thu, 06 Jun 2013 11:17:18 -0400
- 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>
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:
cygdrop cygstart lpr mkshortcut readshortcut winln
What about "cygstart mkshortcut readshortcut"? These may be used by
postinstall scripts, the other stuff is extra, afaics.
IMO man1 pages should be packaged together with their executables.
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.
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-).
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple