Daniel Baumann <[email protected]> writes:

> On 11/12/26 13:49, Simon Josefsson wrote:
>> Are you saying we should make golang-google-cloud track git HEAD?
>
> I don't think that's reasonable.
>
> because all the components are versioned (and differently), just
> having git snapshots in the archive will create a huge mess for other
> packages that (need to) use it: downstreams consumers don't do that,
> they track the tags. modifying all these reverse dependencies to work
> with that.. *uff*

Right, but: Do you have a better idea?

I don't see anything fundamentally different between tracking v0.123.0
or HEAD, both are upstream git 'main' at different points in time.  Of
course, one always needs to make sure all reverse dependencies build
against an updated release first.

>> Bumping this will require an epoch, any objections to doing that?
>
> before doing this, and if you really want to do that, can you
> (briefly) summarize for everyone the reasoning and the packaging
> layout, so that we can refer to this summary for people to know
> what/how/why to deal with.

I am in no hurry, so I'm happy to keep discussing.

Also it seems upstream may have some input in the issue I opened.  Maybe
they will resume pushing the vX.Y.Z or suggest some better method for
us.

/Simon

Attachment: signature.asc
Description: PGP signature

Reply via email to