Hey, On 28/08/19 12:26 pm, Georg Faerber wrote: > On 19-08-28 10:13:53, Utkarsh Gupta wrote: >> Perfecto. >> I just did add a metadata file to include d/upstream/metadata (as we >> discussed in the BoF); rest in on you :D > :) > >> Also, if possible, I'd love to see gem2deb using the correct upstream >> tarballs in d/watch *somehow* instead of what it fetches from rubygems. >> Might take some tweaking but would be worth it :D > I guess we could prefer GitHub if there is consensus for this, which > might also help with including the testsuites, which sometimes are not > included in the gem. Probably, it's possible to find the correct url via > parsing the gem. If nothing is found, the code could fallback to > rubygems. The upstream code is mostly hosted on GitHub, but that's not the case always, no? I am not sure how to do this d/watch thingy because though the homepage mentioned is mostly the URL where the source code is hosted but sometimes it refers to the hosted page or whatever. I tried thinking of something but meh, left it on/for you :P Best, Utkarsh
Attachment:
signature.asc
Description: OpenPGP digital signature