public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* libpng changes...again. [Was: Re: I~M~-build tips Site corrections to be made]
       [not found] ` <3CD6C111.D0E279B6@comcast.net>
@ 2002-05-06 11:26   ` Charles Wilson
  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:07     ` libpng changes...again. [Was: Re: I~M~-build tips Site corrections to be made] Charles Wilson
  0 siblings, 2 replies; 5+ messages in thread
From: Charles Wilson @ 2002-05-06 11:26 UTC (permalink / raw)
  To: Glenn Randers-Pehrson; +Cc: perlspinr, cygwin

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/

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: libpng changes...again. [Was: Re: I~M~-build tips Site corrections tobe made]
  2002-05-06 11:26   ` libpng changes...again. [Was: Re: I~M~-build tips Site corrections to be made] Charles Wilson
@ 2002-05-06 13:03     ` Glenn Randers-Pehrson
  2002-05-06 13:13       ` Charles Wilson
  2002-05-06 13:07     ` libpng changes...again. [Was: Re: I~M~-build tips Site corrections to be made] Charles Wilson
  1 sibling, 1 reply; 5+ messages in thread
From: Glenn Randers-Pehrson @ 2002-05-06 13:03 UTC (permalink / raw)
  To: Charles Wilson; +Cc: perlspinr, cygwin

Charles Wilson wrote:


>
> !@#$!*(@^#$!^@#|*!@#|*!^@#*$^!@#*$^!@#*$^"!(#^$*&^#$(&!^@$(^!#@$
>
> 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!

I'm not removing pkgconfig/libpng.pc

I am merely adding bin/libpng-config for anyone who wants it.
You are free to ignore libpng-config.

Glenn


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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: libpng changes...again. [Was: Re: I~M~-build tips Site corrections to be made]
  2002-05-06 11:26   ` libpng changes...again. [Was: Re: I~M~-build tips Site corrections to be made] Charles Wilson
  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:07     ` Charles Wilson
  1 sibling, 0 replies; 5+ messages in thread
From: Charles Wilson @ 2002-05-06 13:07 UTC (permalink / raw)
  To: Charles Wilson; +Cc: Glenn Randers-Pehrson, perlspinr, cygwin

Charles Wilson wrote:
Ignore previous post.  Bad day.  I'm much better now.  Sorry for the 
trouble.  Move along folks, nothin' to see here...

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: libpng changes...again. [Was: Re: I~M~-build tips Site corrections   tobe made]
  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
  0 siblings, 1 reply; 5+ messages in thread
From: Charles Wilson @ 2002-05-06 13:13 UTC (permalink / raw)
  To: Glenn Randers-Pehrson; +Cc: perlspinr, cygwin

Glenn Randers-Pehrson wrote:

> 
> I'm not removing pkgconfig/libpng.pc
> 
> I am merely adding bin/libpng-config for anyone who wants it.
> You are free to ignore libpng-config.


Yes, I just got finished reading the last two weeks of png-implement. 
(Next I'll start on the US Tax Code...<g>).  I misunderstood your 
earlier email; it sounded like png-config was going to *replace* 
pkg-config/libpng*.pc, which would definitely be a step backwards IMO. 
However, *adding* a png-config is not a bad idea at all; people seem to 
be more comfortable with scripting around those in client configure.in's 
for some reason.

As I said, I'm all better now.  Move along, nothin' to see here...

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: libpng changes...again. [Was: Re: I~M~-build tips Site correctionstobe made]
  2002-05-06 13:13       ` Charles Wilson
@ 2002-05-06 13:53         ` Glenn Randers-Pehrson
  0 siblings, 0 replies; 5+ messages in thread
From: Glenn Randers-Pehrson @ 2002-05-06 13:53 UTC (permalink / raw)
  To: Charles Wilson; +Cc: perlspinr, cygwin

> As I said, I'm all better now.  Move along, nothin' to see here...
>
> --Chuck

#:-)

Now if my colleagues would come to a conclusion about whether
png_zalloc should be exported or not...  I've been yanked back and
forth at least 4 or 5 times  on a short chain about that.  I don't think
it should, but what do I know?

Glenn


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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2002-05-06 20:53 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20020506173533.WFNM28991.mtiwmhc22.worldnet.att.net@webmail.worldnet.att.net>
     [not found] ` <3CD6C111.D0E279B6@comcast.net>
2002-05-06 11:26   ` libpng changes...again. [Was: Re: I~M~-build tips Site corrections to be made] Charles Wilson
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

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