Re: Rebuilding a package after removing a build step

[Suhail Singh]

Vagrant Cascadian <vagrant@debian.org> writes:

> Rather than picking an arbitrary incremental number, I have in the past
> used something based on the results from git describe... e.g. in my
> current checkout of guix:
>
>   $ git describe --match=v1.4'*'
>   v1.4.0-142685-gfc059c66cf
>
> e.g. 142685 commits past v1.4.0, with the commit fc059c66cf
>
> That should *usually* end up in the correct order, although sometimes
> there are surprises. For example, I had to specify --match otherwise it
> picked v1.3.0 for some inscrutible git merge-ordering reason.

That seems like a useful and fairly generally applicable strategy.  Any
reason as to why something like that (which allows for additional
optional arguments such as "--match-v1.4'*'") shouldn't be used as the
default (as opposed to manual revision numbers)?

-- 
Suhail