> Now it does make the logic of the spec files slightly > more complicated, using > logic to enable patches, but I have lots of examples > that work.
hmm, you mean like %if version is <1.2.3 use patch1 %elif version is >=1.2.3 and <= 1.2.5 use patch2 %else use patch3 %endif ?? that'd bring way too much complexity and would be unmanageable IMO. We can have the separation of patches into directories, it has other benefits as well, but to go back a version one would just figure the best revision of the spec and use Mercurial's forces to revert to it. Can we use tags to make it easy to find version changes? http://mercurial.selenic.com/wiki/Tag -- This message posted from opensolaris.org
