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: [ANNOUNCEMENT] Updated: inetutils-1.9.1-1; NEW: inetutils-server-1.9.1-1
Date: Tue, 03 Dec 2013 14:21:00 -0000	[thread overview]
Message-ID: <529DE8AC.8030903@cwilson.fastmail.fm> (raw)
In-Reply-To: <CAKf2h5TSYOC-it3ogMHra+vxvLpfuu9cHsNfOqSLQn5ZqTvsQw@mail.gmail.com>

On 12/3/2013 8:40 AM, Frank Fesevur wrote:
> 2013/11/15 Charles Wilson:
>> CHANGES (since 1.7-2)
>> ========================
>> o Updated to latest upstream release
>> o Rely on cygport to autogenerate setup.hints
>> o Split package into client and server components.
>
> I just tried to install the clients package and got this notification:
>
> inetutils-server    (1.9.1-1)
>      Common networking clients and servers (servers)
>      Required by: inetutils
>
> Why does the "clients" package require the "servers" package?

Transition.  The old (1.7-x) package was monolithic, so the people who 
*wanted* the server(s) only needed to install the 'inetutils' package 
itself.

If I *didn't* add this requirement to the new inetutils package (which 
contains only clients), then those users, when upgrading, would lose 
their server(s) and their system would break.

We don't want that.

So, what I typically do when I break up a monolithic package, is ensure 
that for the *first* update cycle after the breakup, all users will 
still get all the (new) subpackages.

For the *next* update cycle, I'll remove those unnecessary requires: 
statements. (If somebody waits six months to update, misses 1.9-1, then 
THEY might get a temporarily broken system. But that's just too bad; 
can't cater to people who don't keep their systems reasonably up to date).

--
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-12-03 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 22:07 Charles Wilson
2013-12-03 13:42 ` Frank Fesevur
2013-12-03 14:21   ` Charles Wilson [this message]

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=529DE8AC.8030903@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).