Re: [Celestia-developers] Celestia 1.3.2 update
Real-time 3D visualization of space
Status: Beta
Brought to you by:
cjlaurel
From: Christophe T. <ch...@te...> - 2004-08-27 21:32:30
|
Le Vendredi 27 Ao=FBt 2004 22:45, Selden E Ball Jr a =E9crit=A0: > Why? I really don't understand. > > It shouldn't be a bandwidth issue: the kits don't get downloaded from > Shatters.net but from SourceForge's international network of mirror sites. > SourceForge certainly has plenty of storage space, too. > > It shouldn't be an organizational issue: SF provides URLs that > "show only this release", for example. > > In fact, I'd expect the organizational issue to be worse if you have > to upload the kits to any of a large number of independant services. > If one of them gets corrupted for whatever reason, you'll still have > to refer back to an unadulterated version somewhere. Best, I think, > if that "somewhere" is SF. > > What am I missing? What most FOSS projects do is provide an 'official' and supported tarball. Packages for the various distributions are usually contributed, distributed= =20 and supported outside of the project. That's the official policy for the KD= E=20 project for example. The problem if you start distributing packages directly is that you inevita= bly=20 get users complaining: "Why don't you make packages for distribution XYZ?".= =20 Keeping all packages outside of the project is a way of putting all=20 distributions on the same foot. But for me the main point is that apt/yum/urpmi is just a saner way to=20 distribute software. There is no point in keeping RPMS on SF if all the use= r=20 has to do (and should do) is "urpmi celestia-kde". =2D-=20 Christophe |