Hi All,
The number of aircraft in CVS continue to grow at a quite incredible rate. We
now have over 170, and there aren't enough hours in the day to fly all of them
the amount of time that they really deserve. I haven't graphed the number of
new aircraft per month, but it certainly feels that not a day goes by without a
new aircraft directory being created in the CVS logs.
This is a wonderful problem to have, but does mean that running "cvs up" on
the /data directory can take an age, and the amount of data in the data package
in its entirety is quite large.
I wonder if it would be worth moving all the aircraft to a separate repository.
I think this might have a number of advantages:
1) Clearer separation between the core code and the aircraft custom code.
2) Easier administration of CVS write access - it should be pretty
straightforward to give those who maintain a given aircraft write access to
their own aircraft.
3) Easier "cvs up" for those with a slow connection, or not much time. No need
to update all the aircraft all the time.*
-Stuart
* Yes, I'm sure there is a way to write some .cvs file so that the Aircraft
tree is ignored, but I feel there should be an easier way.
___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
