[DRE-maint] Re: Mongrel on Debian - wanna join forces?

Jens Kraemer jk at jkraemer.net
Sat Jan 6 11:30:59 CET 2007

On Sat, Jan 06, 2007 at 12:08:15AM -0600, Gunnar Wolf wrote:
> Jens Kraemer dijo [Fri, Dec 29, 2006 at 01:31:10PM +0100]:
> > > Ok, I have not yet worked with your packages - I'm only downloading
> > > them now. I want to work with what you have done, possibly merge it
> > > with the little I have done. Please tell me, are the packages
> > > available here the latest you have?
> > > 
> > > http://debian.jkraemer.net/apt/pool/main/m/mongrel/
> > 
> > yeah, these are the latest packages.
> Ok. I finally started working on this - As of right now, I uploaded
> into our SVN tree the files as I had worked with them. I supposed most
> (I'd even say that all) of the packaging work you have done is
> contained in the debian/ directory - However, I found quite a large
> diff between the files you have _outside_ of debian/ and the ones I
> have, which I'm attaching to this mail. We worked on the same version,
> so this is not as clear-cut as I'd like - Did you make this diff? Or
> do we have an upstream which changes the contents without bumping the
> version number? Where/how did you get your upstream sources? I
> downloaded them from: 
>     http://rubyforge.org/frs/download.php/13231/mongrel-

I think the diff exists because I built the package not from the
released gem, but from mongrel svn. I checked out the source when 0.13.4
was released. As the author decided to not use tags to mark his
versions, it's quite hard to get the correct revision from svn. I don't
remember changing anything in Mongrel's source.

Imho we're on the safe side if we use the source from the gem from now

> I'm also new to this team, and it seems the package does belong in
> there - at least, there are some pkg-ruby-extras members who are
> interested and willing to work with it :) Anyway, regardless of how
> this is managed: We will (of course, with your permission) build upon
> your fine work. Do you want to be listed as a co-maintainer of this
> package (which means sharing some responsabilities, of course,
> regarding the package well-keeping), or just to be credited as the
> original starter of this effort?

Co-maintainer sounds good - I guess I'll get myself an alioth account 


Jens Krämer
jk at jkraemer.net

More information about the Pkg-ruby-extras-maintainers mailing list