Re: The Archive and version compatability
- Posted by bernie Mar 25, 2009
- 923 views
Why are you worrying about this ??
Any user downloading code from the archive before
ver 3 is not going to be able to use the code unless
they have the binaries so place all that code in a
separate directory called out of date code.
Make a special compatibility list or mark ver 4 code as
it is added to the archive.
Then any code not marked ver 4 should be only used on
ver 3.
Bernie, There are plenty of things in the archive that work with 2.5, and some people may still have 2.5 installed on their system. Further, we do not have control of the archive, we cannot move anything. Even if it were moved, that would require changes to the archive script which RDS doesn't want to do right now. As for the special compatibility list or marking for 4.0, that too would require changes to the script. So, we are trying to figure out how to work within the confines we have been given.
Now, it's very possible to have code that works on 2.x, 3.x and 4.x w/o issue, so we need some way of indicating that as well.
Jeremy
Some code 2.5 and before is shrouded how are you going to
deal with that.
Who is going to go through all the code in the archive and
decide what version it's for and try it and mark it??
Who is going to spend the hours of answering questions
about how to change the old code to work with ver 4.
As for me I am writing new code for ver 4.0 to take advantage
of the new features and pulling my old code from the archive
I think your creating a lot of work that no one is going to
volunteer to perform.
