Re: revbumps and version sharing

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Mon, 23 Nov 2009 15:33:41 +0100
    From:        Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
    Message-ID:  <20091123143341.GA17230%britannica.bec.de@localhost>

  | At the top of the file.

Ah, OK, thanks, I can see that in many Makefile.common files, but not all
(and in particular, not in cdrdao's).

cube%cubidou.net@localhost said:
  | I don't think that kind of stuff kind be automated in a really sane way.
  | There will be use cases that will slip through eventually, and the pain will
  | only be relocated.

Sure, nothing is perfect, especially when dealing with human interactions,
the aim is just to reduce the problems, not make everything go away.

Always leaving PGKREVISION once it is set, and just incrementing it
forever is certainly a plausible (and simpler) reaction.

gdt%ir.bbn.com@localhost said:
  | Also, note that someting going from 1.2.2nb6 to 1.2.3nb6 is not an actual
  | problem, just a cosmetic annoyance. 

Yes, I was aware of that, it was the step backwards that I was
commenting on - it is because developers just naturally do that
when a new version is involved, PKGREVISION just goes, that I was
looking for a way to avoid that being a problem, by preventing the
1.2.3nb6 version from ever existing.

Changing habits, and never deleting PGKREVISION would work too.

kre