On Sat, Apr 07, 2012 at 05:17:32PM +0300, Dmitry Borodaenko wrote: > On Mon, Apr 2, 2012 at 23:35, Cédric Boutillier > <[email protected]> wrote: > > If the library you are maintaining appears to be released as a > > gem, you can benefit from the "gem2deb" tool, which takes care of > > most of the points mentionned above in an automatised way.
> This might confuse people into thinking that gem2deb won't work with > ordinary tarballs. How about this replacement for the above: Thanks Dmitry for the review. > The "gem2deb" tool takes care of most of the points mentioned above in > an automatised way. Running gem2deb on your orig tarball or a gem > package from your upstream will get you most of the way towards making > your package compatible with the new draft Ruby policy. I've integrated your proposition in the draft on gobby.debian.org. I also did a s/less than three months/about two months/ for the date of the freeze. Best regards, Cédric
signature.asc
Description: Digital signature
