Re: Dealing with upstream only releasing gems
- To: debian-ruby@lists.debian.org
- Subject: Re: Dealing with upstream only releasing gems
- From: Gunnar Wolf <gwolf@gwolf.org>
- Date: Fri, 9 Apr 2010 19:06:22 -0500
- Message-id: <[🔎] 20100410000622.GC6294@gwolf.org>
- In-reply-to: <20100330071123.GC26286@density.luon.net>
- References: <20100329235938.GA7435@connexer.com> <20100330055114.GA32333@xanadu.blop.info> <20100330071123.GC26286@density.luon.net>
Paul van Tilburg dijo [Tue, Mar 30, 2010 at 09:11:23AM +0200]:
> > You can easier use githubredir.debian.net to use the github repository
> > as the source, or simply repackage the gem as a tgz. It would be a good
> > thing to have a gem2tgz script that does that automatically, btw.
>
> AFAIK in the case of libi18n does upstream not tag releases, so
> githubredir doesn't offer any tarballs. It is also the reason you
> cannot create any watch-file. Since this is all about upstream, we
> should really encourage them to at least tag there stuff. Packaging and
> maintaining in essence "release/version-less" software is undoable.
> Even more so if it is team-maintained since you might know what the
> situation is but not the other team members.
Of course, you could use versioning as 20100409 - if you are confident
enough with the system, of course, to know when upstream has reached a
"good" point.
--
Gunnar Wolf • gwolf@gwolf.org • (+52-55)5623-0154 / 1451-2244
Reply to: