Then the changelog would say "Non-maintainer upload." :)
> I assume you mean patches? If so, sorry, but why not?
Yeah, that's what I meant. Just because we don't like to deviate unnecessarily from Debian. I wouldn't change source format in an NMU either (but then I guess I'm pretty conservative when touching other people's packages in Debian).
One of the advantages of 3.0 (quilt) is that you don't need to add a patch system to add a patch neatly, it's already there.
IIRC 3.0 (quilt) is supported all the way back to etch, so backporting shouldn't be a big deal either.
The indirect dependency is fine with me (esp. as I prefer not deviating unnecessarily in Ubuntu). The python helpers provide dependencies on python I'd have expected the same for ruby, but as I said I'm completely unfamiliar with it.
> Even if I NMU it into Debian? ;-)
Then the changelog would say "Non-maintainer upload." :)
> I assume you mean patches? If so, sorry, but why not?
Yeah, that's what I meant. Just because we don't like to deviate unnecessarily from Debian. I wouldn't change source format in an NMU either (but then I guess I'm pretty conservative when touching other people's packages in Debian).
One of the advantages of 3.0 (quilt) is that you don't need to add a patch system to add a patch neatly, it's already there.
IIRC 3.0 (quilt) is supported all the way back to etch, so backporting shouldn't be a big deal either.
The indirect dependency is fine with me (esp. as I prefer not deviating unnecessarily in Ubuntu). The python helpers provide dependencies on python I'd have expected the same for ruby, but as I said I'm completely unfamiliar with it.