public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Attn: Yaakov [Was: Re: cygutils Postinstall Script Errors With Exit Code 128]
Date: Wed, 05 Jun 2013 16:47:00 -0000	[thread overview]
Message-ID: <51AF6B99.2000006@users.sourceforge.net> (raw)
In-Reply-To: <20130531083445.GA30659@calimero.vinschen.de>

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

  reply	other threads:[~2013-06-05 16:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 16:04 cygutils Postinstall Script Errors With Exit Code 128 Reini Urban
2013-05-29 19:50 ` Paul.Nickerson
2013-05-29 23:51 ` Attn: Yaakov [Was: Re: cygutils Postinstall Script Errors With Exit Code 128] Charles Wilson
2013-05-30  0:43   ` Yaakov (Cygwin/X)
2013-05-30 10:27     ` Corinna Vinschen
2013-05-30 21:26       ` Charles Wilson
2013-05-31  8:51         ` Corinna Vinschen
2013-06-05 16:47           ` Yaakov (Cygwin/X) [this message]
2013-06-06 15:17             ` Charles Wilson
2013-05-30 20:50     ` Charles Wilson
2014-07-16  1:54 ` cygutils Postinstall Script Errors With Exit Code 128 dylanhay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51AF6B99.2000006@users.sourceforge.net \
    --to=yselkowitz@users.sourceforge.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).