but I’m trying to stay in sync with your CVS repository while installing
ROOT by RPM and avoiding to compile all the stuff that is not changed.
All is done except for a stupid curiosity about release tags in you reposiroty.
I set up a first repository with “-r v4-04-02” option that now is “sticky” on mine.
Since now I have to check for updates on “v4-04-02-patches” tag?
Is this a “updated” version respect to the first one that is stuck to the
source version available with tarballs?
The name v4-04-02-patches is always the same regardless modifications of
source files?
you can now checkout v4-04-02a which is the first bug fix tag on the stable v4-04-02-patches branch. You can stay on this branch and just do cvs update to get the latest fixes.
Thanks for your suggestion, otherwise I had been in sync with the "-patches"
one…
But, then, what is the tag “vx-xx-xx-patches” for?
A last question (I know I’m boring…):
As v04-04-02a is a “stable” name for the updates an bugfixes of
v04-04-02, is there a way to “tag” the different patches achievable from
v04-04-02a?
To say better, how can I distinguish different version of patches?
Only by release date?
[quote=“germano”]Thanks for your suggestion, otherwise I had been in sync with the "-patches"
one…
But, then, what is the tag “vx-xx-xx-patches” for?
A last question (I know I’m boring…):
As v04-04-02a is a “stable” name for the updates an bugfixes of
v04-04-02, is there a way to “tag” the different patches achievable from
v04-04-02a?
To say better, how can I distinguish different version of patches?
Only by release date?
Regards, Germano[/quote]
Only now I see how much odd was my question and that I read only the first
few words…
I apologize
As posted some time ago, I tried to stay in sync with your
v4-04-02-pacthes branch to be up to date. I tried also to
save past compilation objects to minimize the number of files
to be compiled again.
When I passed from v4-04-02 to v4-04-02a everything goes like
I wanted: a few files needed to be compiled again, giving me back
all the efforts spent to build up an RPM packaging system that took
as few as possible time to be generated.
From version v4-04-02b was chosen to modify the file RVersion.h to
incorporate directòy this info into ROOT.
Looking at the time I spent to pass from “a” to “b” version (only very few files
were changed) I guess that a modification in the above file causes a heavy
rebuilding (50% ?) of ROOT, due to dependencies.
Is this unavoidable? Am I wrong? I’m scaried to pass to version “d” .
[/quote]