make force-tag gone

[Jeffrey Ollie]

On Tue, Sep 9, 2008 at 11:03 AM, Denis Leroy <denis at poolshark.org> wrote:
>
> There's no logic here. You're not forcing people to tag after every CVS
> check-in, as far as I know. If a release 'n' fails to build (for example,
> because you forgot to check-in a patch), it makes zero sense to bump to n+1,
> because release 'n' never *existed* in the first place, since it was never
> built. That has zero impact over auditing. Spec file auditing is done
> through CVS.

force-tag can also be used to move the tag of a package that *was*
built, if you're not careful.  That's the situation we need to avoid.
You can also view tagging as "I intend to build this".  Why shouldn't
we be able to track failed builds?  It was submitted to Koji so even
though it didn't result in a set of packages there was some effect on
the system.

Refusing to bump a release number and re-tag because you don't want to
"look stupid" is not a technical argument.

And before you ask, yes I've used force-tag before even though I know
I shouldn't.  Removing it will help me be a better package manager.

-- 
Jeff Ollie

"You know, I used to think it was awful that life was so unfair. Then
I thought, wouldn't it be much worse if life were fair, and all the
terrible things that happen to us come because we actually deserve
them? So, now I take great comfort in the general hostility and
unfairness of the universe."

	-- Marcus to Franklin in Babylon 5: "A Late Delivery from Avalon"