On Wed, 2006-03-01 at 18:49 +0100, Tels wrote:
> Moin,
> 
> On Tuesday 21 February 2006 19:19, chromatic wrote:
> > On Monday 20 February 2006 11:27, Chris Hinrichs wrote:
> > (That reminds me, we really ought to merge the three separate branches
> > soon.)
> 
> What three branches!?

I believe chromatic is referring to the following three branches:
      * the one in CPAN (David Goehrig is officially in charge of this
        one)
      * chromatic's branch (I don't have a link, but I think these are
        available as tar files through links from sdl.perl.org)
      * my branch which is in a subversion repository
        (http://phux.net/websvn/ -- there isn't anonymous svn access to
        this repo).

As far as I know, all my changes have made it upstream (except for maybe
the most recent one that fixes a problem with SDL::App's return value),
so mine technically isn't a branch or fork.  Nor was it ever intended to
be.  When development was slow because David was in Europe backpacking
(my memory is hazy in this regard), I still needed to store my changes
someplace and track the changes I made, so I made my own repo.

I think there may also be another branch/fork floating around out there
that is equivalent to mine (in that someone made it in order to keep
track of their updates until everything was merged).

I think we should work on an entirely new release that incorporates
everything we currently have and then stick a version 3 on it (and
assert its compatibility with Frozen Bubble so distributions will
actually package it (I've seen some distributions package only
SDL_perl-1.x because Frozen Bubble claims to need that version
explicitly even though FB works fine with 2.1; this is hindering
adoption of the latest and greatest)).  Also, since your time is
limited, David, what does it take to get other people access to the
official repo on perl.org (or whatever) and to create CPAN distributions
(I have never interacted with CPAN from that angle, so I don't know much
about it).

-- 
Andy Bakun <[EMAIL PROTECTED]>

Reply via email to