From: Ian Scott <ian.scott@st...> - 2003-06-03 10:16:00
Hi VXL users.
As some of you may have already noticed, we have been performing major
surgery on the repository over the past week.
The aim of this edit was to replace the old imaging library vil. The new one
has been in use under the name vil2 for the past six months. It is more
powerful, faster, and in our opinion easier to use. It has all the major
features of the old vil (now called vil1) and some new ones.
The VXL-maintainers decided that the old and new vil libraries should be
renamed to reflect this change in status. Last Friday, the old vil was
renamed to vil1 and vil2 was renamed to vil.
All of this will have several effects on you as users.
1. If you update your copy of VXL from CVS, then you will need to delete
your vxl/core directory before updating again.
This is because your local CVS will be confused by the edits we performed
directly on the repository.
2. As a user of the old vil or vil2 you will need to update your local code
to deal with the changes. The following procedure should rename all of your
code. Be careful to run the two scripts in the correct order.
A. You will need a copy of perl on your machine, and an update-to-date VXL
B. Make a complete copy of your private source tree and keep it somewhere
C. Run perl my_vxl_src/core/vil/scripts/convertviltovil1.run_me_first.pl
D. Run perl my_vxl_src/core/vil/scripts/convertvil2tovil.run_me_second.pl
E. That's it. The scripts will have made copies of any files that they
modified, ending in .old or .old2, which you can delete.
3. vil1 will stop being supported sometime in the future, but it will remain
in the repository to support legacy code. If you want to convert any
existing code to use the new vil have a look at
Ian Scott and the vxl-maintainers.
From: Peter Vanroose <Peter.V<anroose@es...> - 2003-06-03 10:26:42
> 1. If you update your copy of VXL from CVS, then you will need to delete
> your vxl/core directory before updating again.
This is not necessary (and actually not advisable if you do not want to
throw away any local changes).
You only need to remove or rename the core/vil directory tree , and make
sure you "cvs update" core/vil1 (which did not exist before) and remove
core/vil2 (which will otherwise remain in place).
The renamed old vil and the new vil1 should be identical, except for the
name changes (as done by the perl scripts, as explained by Ian).
Idem for the new vil and the deleted (or renamed) vil2.
From: Andrew Fitzgibbon <awf@ro...> - 2003-06-03 12:31:31
And I'd just like to take the opportunity to offer
a public "thank you" to you for the effort gone into
making this change. It's a real improvement to
VXL, and it has been done remarkably cleanly and
efficiently. The whole procedure has been really
well managed, and the community will benefit from
it for a long time.
From: Peter Vanroose <Peter.V<anroose@es...> - 2003-06-03 12:55:22
> And I'd just like to take the opportunity to offer
> a public "thank you" to you for the effort gone into
> making this change. It's a real improvement to
> VXL, and it has been done remarkably cleanly and
> efficiently. The whole procedure has been really
> well managed, and the community will benefit from
> it for a long time.
Yes indeed! Thanks for all the efforts, and thanks to all people
in Manchester for donating their image software to the vxl community.