X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <48B1E9E5.8030704@users.sourceforge.net>
Date: Sun, 24 Aug 2008 18:08:21 -0500
From: "Yaakov (Cygwin Ports)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: man: cygwin 1.7.0 and special filename chars
References: <48AF247F DOT 2050300 AT users DOT sourceforge DOT net> <48AF79A9 DOT AE50661A AT dessent DOT net> <48B0E0FF DOT 1090508 AT users DOT sourceforge DOT net>
In-Reply-To: <48B0E0FF.1090508@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yaakov (Cygwin Ports) wrote:
> With 1.7, there is no such issue; make manifypods builds OOTB.  So any
> such workaround would have to be caught in the cygport postinstall
> stage, maybe in __prepman().  But I'm not sure that it would be at all
> necessary.

BTW, this would still be insufficient:  if someone builds the gtk2-perl
packages without cygport, e.g. with CPAN or manually (which is now
possible), there will be nothing to "fix" their manpages.  So this needs
to be fixed in man.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEUEAREIAAYFAkix6eUACgkQpiWmPGlmQSMA7wCYgDh8PynPs/vhJsKKyCb2jz+6
BgCg9L4tH9M5jD5b+icMlCaLbkrtVSk=
=Xg42
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/