X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=R51Yg4VIZv+57Vf3D458/mk242ZXO5AZnUVXxWGtN+BIsLv4FhSFq
	brvtfy3Yu/EDwVk2HAVZKchg8tKuLXPSqHJVWHITggpSuChUhAcjdyxFI1nPFUXT
	1l0rdg832F43p8yQcU7n+xcJWkIwhm2gU94RZFYMnG11vz94JdTPp8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=N38NOJYN14zdwSa7QPniiTF1Wgc=; b=di2r0JNvse+GYNsZnUWG7TlPB7ld
	v6jB9AFPG6hjIf1lJB7RKLXLze03cGGVQQok6wk7KPtCNMGvTd6URVJ1nmfag/zs
	84z30IZr+qWMi/F8yb9ZrvxI/iLre9HR8BDrvQJ3yzc8i77x9bC/0fWScvCaJlTD
	bMXpIGPYeWf/u30=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18Emoe3XRFpSST69KC1ez1H
Date: Mon, 13 Jan 2014 13:22:52 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Base 64-bit Cygwin now requires Perl?
Message-ID: <20140113182252.GB7186@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAAXzdLX=PuGT8N9G19W8ykN7H6zLa5D5psXc+SMmyZfogMg5CA AT mail DOT gmail DOT com> <52D424E6 DOT 7010105 AT etr-usa DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52D424E6.7010105@etr-usa.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Mon, Jan 13, 2014 at 10:39:50AM -0700, Warren Young wrote:
>On 8/9/2013 11:17, Steven Penny wrote:
>> Because of this dependency line
>>
>> man
>>   groff
>>    perl
>
>The groff package includes several helper programs written in Perl: 
>afmtodit, groffer, and grog.
>
>Red Hat and Mandriva split these utilities out into a separate 
>package[*] but that would be something you'd have to prevail on cgf to 
>change.

Actually, I didn't upload the 64-bit groff.  This is one of the reasons
why I had reservations about people other than the package maintainers
uploading packages.  The end result is that I'm forced to deal with
someone else's decision.  This has been the case for a few of my
packages, uploaded during the 64-bit transition.  If I had created the
package I might have paused at the perl dependency since clearly groff
is part of base.

In retrospect, it would have potentially made sense to use the same
versions and packaging for the 64-bit as for the 32-bit.  That might
have minimized this type of problem.

cgf

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