On Sun, 18 Sep 2016 14:23:51 +0200 Klaus Zimmermann wrote: [...] > I had a quick look and it seems upstream doesn't prepare releases > anymore, offering simply the latest github master as a tarball to the users. > > Is this correct?
It seems so, as the homepage [1] states: | Users are strongly encouraged to use the most recent software in the | GitHub repository and not the tarballs! [1] https://hplgit.github.io/doconce/doc/web/ > > Should we still package something? > What do more experienced packagers than me think about it? I was hoping to see some reply from other Python Applications Packaging Team members (which I am not!), but, since no reply has arrived, here's my own humble opinion: I personally think that Debian package maintainers should package whatever upstream considers a "release", be it a tar archive or even just a git repository tag. In the present case, I think upstream should be contacted and encouraged to begin tagging (from now on) specific points of history in the git repository (that's basically what GitHub appears to call "releases"). This is what the Debian package should ship, in my own personal opinion. I hope this can be done soon. Thanks for your time! Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpmo8Jxlu2Uf.pgp
Description: PGP signature
