On Tuesday 25 March 2003 6:41 am, Richard Bytheway wrote: > As a pay-by-the-minute modem user, I would prefer not to have 200MB of data > dumped into the base package CVS if possible. The cheapest my connection > gets is �0.48 per hour. 200MB is about 20 hours of download time, thus > costs about �10 (US$16 or so), and my phone line is busy for a day. >
Uh, actually 200MB is a the entire Repository. A full checkout is 132MB and you only have to do it once. You can download a 30-40MB nightly snapshot and start your repository that way. If you're only interested in certain nodes of the tree, you don't have to checkout from the head. > I think that splitting the base package into two branches/repositories > would work best, one for what is needed at runtime, and one for the source > files (everything else). I am not in favour of separate branches for > different aircraft, or even one new branch for optional aircraft, since CVS > is used by people who want the latest features, thus new features should > appear in CVS, not elsewhere. > Speaking as the guy that does the tagging I agree with the latter, but regarding the former, the bulk of the repository is textures. The only "source" stuff is 4 MB of TeX and ps files in the Docs folder. > People who want to play with the source files can then take the decision to > download however many MB of data, but for those of us on modems with no > graphical abilities can avoid the pain. > > For the runtime texture files, would is be possible to switch to a format > with lossless compression, such as png? Whilst it does not save on video > card memory usage, it has a minor (negligible) benefit for hard disk space, > but could have a significant benefit on download times. > > Richard > > > > m. :-) > > > > And I have another 200MB of xcf files for hi-res C172-S Panel > > > > :o). IMHO one > > > > and only solution is to make new CVS branch for it. I'am > > really interested in > > source files of some 3d panels and aircrafts. > > > > Madr > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
