public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cwilson@ece.gatech.edu>
To: Glenn Randers-Pehrson <glennrp@comcast.net>
Cc: perlspinr@att.net, cygwin@cygwin.com
Subject: libpng changes...again. [Was: Re: I~M~-build tips Site corrections to be made]
Date: Mon, 06 May 2002 11:26:00 -0000	[thread overview]
Message-ID: <3CD6CB09.7080902@ece.gatech.edu> (raw)
In-Reply-To: <3CD6C111.D0E279B6@comcast.net>

Glenn Randers-Pehrson wrote:

> Also, if you haven't noticed on png-implement, libpng
> will be providing libpng-config starting with version
> 1.2.3.  Of course that still leaves problems detecting
> older versions.  Also, png.h and pngconf.h are going
> to be restored to their old locations in /usr/include or
> whatever, as links from their new locations in
> /usr/include/libpngNN.  Again, leaving problems for
> people who have libpng-1.2.2.

!@#$!*(@^#$!^@#|*!@#|*!^@#*$^!@#*$^!@#*$^"!(#^$*&^#$(&!^@$(^!#@$

I give up.  I am about an inch away from relinquishing maintainership of 
the official cygwin libpng package.  This is just too much.

What the hell was wrong with pkg-config?  Why not just stick with that; 
everyone else in the world is moving from foo-config to pkg-config/pc 
files!  Here, I thought png was being smart and ahead of the curve and 
forward thinking by skipping the whole 'foo-config' stage and going 
straight for pkg-config!

Geez, there's even a native windows port of pkg-config.

It's a good thing I never got around to officially uploading the 
cygwin-libng-1.2.2 package.  do you know that libpng takes more care and 
feeding than any other package I maintain except for cvs...

somebody on the cygwin mailing list was just hectoring me about my 
refusal to support another package, the ungrateful wretch.  "How much 
time does it really take?" they asked.  Harrumph.

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

       reply	other threads:[~2002-05-06 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020506173533.WFNM28991.mtiwmhc22.worldnet.att.net@webmail.worldnet.att.net>
     [not found] ` <3CD6C111.D0E279B6@comcast.net>
2002-05-06 11:26   ` Charles Wilson [this message]
2002-05-06 13:03     ` libpng changes...again. [Was: Re: I~M~-build tips Site corrections tobe made] Glenn Randers-Pehrson
2002-05-06 13:13       ` Charles Wilson
2002-05-06 13:53         ` libpng changes...again. [Was: Re: I~M~-build tips Site correctionstobe made] Glenn Randers-Pehrson
2002-05-06 13:07     ` libpng changes...again. [Was: Re: I~M~-build tips Site corrections to be made] 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=3CD6CB09.7080902@ece.gatech.edu \
    --to=cwilson@ece.gatech.edu \
    --cc=cygwin@cygwin.com \
    --cc=glennrp@comcast.net \
    --cc=perlspinr@att.net \
    /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).