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:subject:from:to:date:in-reply-to
	:references:content-type:mime-version:content-transfer-encoding;
	 q=dns; s=default; b=l9vcUlsWOTOYTnJ26VPxgfGsQR681+XeePptONoDSbK
	i7KOt0nw+yecoI1YC2O0pNq0Nk2zE2+b3zhjpN5xRlcFKrgV/s0vcppnFwmO83eb
	Q1YIASWTlzOEWrk4/7tnUaMSIwthE7PN7XjqGvQm6HOtnErFO7fmII95Xx7GWkFY
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <1423442255.8420.3.camel@cygwin.com>
Subject: Re: why does libpng16 require libpng-doc?
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Date: Sun, 08 Feb 2015 18:37:35 -0600
In-Reply-To: <khgfda1daprrna24k9150onumksfkb3qke@4ax.com>
References: <khgfda1daprrna24k9150onumksfkb3qke@4ax.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Sun, 2015-02-08 at 15:08 -0500, Andrew Schulman wrote:
> As of now, libpng16 requires libpng-doc.  Is this a mistake?  It seems to defeat
> the purpose of splitting the docs into a separate package, since we have to
> install both.  And for those of us who are only getting libpng16 because it's
> required by another package, we're forced to install libpng-doc too.

libpng-doc only includes the standard license and README docs, and a
single manpage; it is not an extensive API documentation package.  But
it may cause more confusion than intended, so I'll juggle things around
again in -2.


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