Hi, The upstream project https://github.com/marten-seemann/qtls seems to release "new" repositories for the same library for each golang release, for instance
https://github.com/marten-seemann/qtls-go1-16
https://github.com/marten-seemann/qtls-go1-17
https://github.com/marten-seemann/qtls-go1-18
.
.
so on
And we have been packaging these as new source packages for every golang
release.
This is needed, as some other packages depend upon it.
I find it incredibly stupid to be done for every single golang release, and
hence here
is what I propose to be done from next golang(1.20) release.
- - Create a single source repository, for insance
"golang-github-marten-seemann-qtls-go"
- - Keep updating import-path and d/watch pointing to different repo with each
golang release
- - Upstream starts its tagging from 0.1.0, for each go release the revision
numbers can be of form 0.1.0+go1.xy-<debian-revision>
The downside of such a revision is that it'd be hard to update this package for
new upstream revisions, but I took
a look at multiple upstream diffs, and the changes are not much, infact they
are minimal post first release, so this
could be doable, for instance applying new release code as patch.
I know this is sub-optimal, and hence I am looking for opinions, what do you
think about it?
PS: For current golang-1.19 release, I have packaged and uploaded the new
source package with 1.19 suffix to
new so this discussion is not relevant for current release, but definitely for
future ones.
--
Best,
Nilesh
signature.asc
Description: PGP signature
