-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
> nece
"Yaakov (Cygwin Ports)" wrote:
> Am I missing something here?
Apparently my understanding of FAT is wrong then.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
> Oh. I see. That's unfortunate. But I don't understand something: I'm
> looking at the documentation for ExtUtils::MM_Cygwin which claims to
> contain platform-specific overrides for ExtUtils::MakeMaker, one of
> which is rep
"Yaakov (Cygwin Ports)" wrote:
> It's not a case of using the same workaround. With 1.5, the make
> manifypods target would first build the PODs, then create the manpages,
> and would fail when trying to create a manpage containing '::' (as it
> did not use a managed mount). gtk2-perl.cygclass w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
> 3) Perpetuate the s/::/./ workaround in Cygport so that manpages
> continue to be generated with '.'.
It's not a case of using the same workaround. With 1.5, the make
manifypods target would first build the PODs, then create
"Yaakov (Cygwin Ports)" wrote:
> 1) Completely remove the /::/./ substitution in both man and perl for 1.7;
> 2) Have man look for both '.' and '::'.
How about
3) Perpetuate the s/::/./ workaround in Cygport so that manpages
continue to be generated with '.'.
Rationale: Support for : in filenam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Currently man(1) and perl work around Cygwin's inability to handle
illegal DOS filename characters by substituting '.' for '::', IOW:
$ man ExtUtils::Depends
will display ExtUtils.Depends.3pm, which is created by perl on Cygwin
instead of ExtUtils:
7 matches
Mail list logo