Hello Boyuan, thanks for your efforts. On 03/08/2017 11:53 AM, Boyuan Yang wrote: > * For new d/watch file: I had a hard time making decisions and finally chose the > sf.net redirector provided by qa.d.o, which points to flightgear *main* project > tarballs. The lack of an upstream tarball is the main reason I didn't bother to continue to package fgrun. I might be old fashioned, but if upstream doesn't care bundling a tarball, I don't think the software is worth packaging. I kind of allow developers to out-source that task (i.e. to github) and only provide tags. Unfortunately, I didn't find a similar solution with Sourceforge, yet. (It seems it's all there, but uscan would have to be extended to handle Sourceforge.) How did you generate the tarball? For me to sponsor the package (and justify re-introducing it into unstable), I'd at least want a get-orig-source target that automates the process of obtaining a tarball. > Fgrun is now a subproject of flightgear ... ...eh, no more or less than it used to be, before, AFAIUI. > and I really couldn't find a > better page to parse releases or even git tags. Exactly. Kind Regards Markus Wanner
Attachment:
signature.asc
Description: OpenPGP digital signature