-----BEGIN PGP SIGNED MESSAGE-----

Moin,

On Saturday 26 November 2005 11:11, Andy wrote:
> On Sat, 2005-11-26 at 10:27 +0100, Tels wrote:
> > Not to discourage you but what version of SDL are you using/patching
> > against?
> >
> > I lost the overview on what is current and where.
>
> sdl.perl.org says 2.1.0 is new, but that news entry is dated 2004.  The
> link takes you to CPAN, where the latest is 2.1.3.  My patches will be
> against the contents of the 2.1.3 tarball, until a newer version comes
> out.  I have 2.1.3 installed in my perl system directories, and my
> modified files go into a local ./lib sub-directory of my current
> project for testing and diff-generation.

http://search.cpan.org/~dgoehrig/SDL_Perl-2.1.3/ is from 2005-10-05, so 
fairly recent, but the changelog hasn't been updated. David?

> I'm not grabbing stuff from SVN since I want to work from currently
> available releases, rather than be bleeding-edge.

I couldn't even say where the SVN repository is :)

> I appreciate the fact that all my previous patches (back from 2003 and
> 2004) made it into the public release (and the cleanup/integration of
> my SDL::Event::set_type into SDL::Event::type made much more sense).

As I said, I lost track of my contributions. Rather sad :/

Best wishes,

Tels

- -- 
 Signed on Sat Nov 26 11:27:01 2005 with key 0x93B84C15.
 Visit my photo gallery at http://bloodgate.com/photos/
 PGP key on http://bloodgate.com/tels.asc or per email.

 "Any sufficiently advanced technology is indistinguishable from a rigged
 demo."  -- Andy Finkel, computer guy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iQEVAwUBQ4g4z3cLPEOTuEwVAQEIsAf/SHih84hX27TL4gQIhl90gEW7e+ORNWeg
yo3+8uyHLx8ciJswji9lTSwxOe3U2q6vvCrMS8mIeC2meIBVQDbBpjb9Zorg1nZf
e5rUr/zc2WVAV1rZ72wmnbyjA4dhsasfQlkx9rc7Nlm8ZEFGDBXElFngXEQR7utZ
HzWJ71sGlb6RdZ7GzSY93dJRDt7v1XMIabavHUKcOgUn1B1dxnwEa5Vi4R4ns7R6
fvYT0wdzeIunl2DPVcA7AL0BExhbuq52iZtXNDzPKgFDQn2ipovk0SzkVEqt51SJ
7mZNcDgXKYaEl1mt15TrGi9lqsZOIt0DwUEC4NI2jk9xvWzG3T0P3Q==
=C7Gd
-----END PGP SIGNATURE-----

Reply via email to