NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall in <199911192358.PAA24109@kiev.wall.org>
Did I say I expect Perl to do the right thing? :-)
--Larry Wall in <199911200217.SAA24898@kiev.wall.org>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Easy solution to the distribution thing (Score:1)
What we do with Perl::Dist (the toolkit we use to build Strawberry) is to avoid pulling from the original sources entirely (since they are far too unreliable).
Instead, we download the tarballs to a known-good location (I use http://strawberryperl.com/packages/ [strawberryperl.com]) and then the Alien/etc module hardcodes in that path instead.
Since you aren't modifying the tarball, there should be no legal problems.
Reply to This
Re: (Score:1)
I wouldn't be modifying the WebKit tarball, but I did modify the Microsoft gdiplus headers. That would probably make them a no-go for making available elsewhere; I suppose the best I could do would be a script to apply my changes to a set downloaded from the MS site.
gdiplus is only needed for compiling with wxGraphicsContext though, which isn't actually required (as I'd thought), wxDC will do. I'll probably try putting a WebKit tarball up somewhere, depending on what it look like when the build system chang