public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Where is getclip?
Date: Wed, 19 Jun 2013 14:51:00 -0000	[thread overview]
Message-ID: <51C1BFFA.9090708@cwilson.fastmail.fm> (raw)
In-Reply-To: <33EC3398272FBE47B64EE3B3E98F69A753DFAF1B@de011521.schaeffler.com>

On 6/19/2013 10:16 AM, Lemke, Michael SZ/HZA-ZSW wrote:
> On Wed, 19 Jun 2013 10:06:49 -0400 Charles Wilson wrote:
>> On 6/19/2013 9:59 AM, Lemke, Michael SZ/HZA-ZSW wrote:
>>> Is that intended?
>>
>> Yes. Install cygutils-extra. See:
>> http://cygwin.com/ml/cygwin-announce/2013-06/msg00007.html
>>
> Thanks for the quick reply, I found it.  Nevertheless, all I did was updating
 > cygwin and suddenly installed stuff was gone.  Not funny.

Ordinarily, package splits such as this one would ALSO incorporate 
modifications to the package requirements list, so that this sort of 
thing doesn't happen.

That is, the "slimmed down" cygutils package would 'require:' the 
cygutils-extra and cygutils-x11 packages, so that anybody who previously 
had the "old, fat" cygutils package installed would automatically get 
the two new packages, as part of the upgrade -- and would so no visible 
changes in their installation.

However, the purpose of this package split was specifically to *cut 
down* on the default installation footprint of cygutils -- because 
several elements in the 'Base' category require cygutils (specifically, 
they required mkshortcut, readshortcut, and cygstart).  Thus, in THIS 
case, we could NOT do the "normal" thing in manipulating the 
requirements specifications.

Which means..."I updated cygwin and suddenly installed stuff was gone". 
There just wasn't any better solution available.

Sorry for the trouble.

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

  reply	other threads:[~2013-06-19 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 14:28 Lemke, Michael  SZ/HZA-ZSW
2013-06-19 14:51 ` Charles Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-06-19 15:04 Lemke, Michael  SZ/HZA-ZSW
2013-06-19 14:07 Lemke, Michael  SZ/HZA-ZSW
2013-06-19 14:16 ` Charles Wilson

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=51C1BFFA.9090708@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --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).