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=JxA2phgwptAH1uFVstrMz/G6Gf66MgxgmS51zQ1xfL7
	BT/0iml6/Hg9pfnjF25mdh/XSqydPJ22MvgofiJpxGbSbiyPhIERnT/63Nzkij8G
	8DGILudt0L5INRDbjZ4SaFVOCQRI0TSY4zJGV8etNjqxXwlcbaNZh6k2JwB6xvlY
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <529DE8AC.8030903@cwilson.fastmail.fm>
Date: Tue, 03 Dec 2013 09:20:28 -0500
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: inetutils-1.9.1-1; NEW: inetutils-server-1.9.1-1
References: <announce.20131115220328.1C017680096@frontend2.nyi.mail.srv.osa> <CAKf2h5TSYOC-it3ogMHra+vxvLpfuu9cHsNfOqSLQn5ZqTvsQw@mail.gmail.com>
In-Reply-To: <CAKf2h5TSYOC-it3ogMHra+vxvLpfuu9cHsNfOqSLQn5ZqTvsQw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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