Am Mittwoch, 29. September 2010, 18:33:39 schrieb Mike Noyes: > On Wed, 2010-09-29 at 08:52 +0200, Martin Hejl wrote: > -snip- > > > But either way - I didn't mean to start a "which versioning system > > should we use" discussion, especially since it doesn't matter to the > > problem at hand - no matter which versioning system is used, the source > > tarballs still need to be uploaded into the File Release System. > > Everyone, > That is my understanding of the situation also.
I thought a bit about this issue (and vaguely remember we had this discussion years ago :)) I understand, that if wrote and release an editor I have to provide the sources as well and cvs does not be good enough. But what should the tarball in our case contain? We do have packages build from sources written by anyone else and available elsewhere on the net. (That we do have some of them in our cvs repository is just for our convenience). I doubt SF asks us to provide each and every source we use in our packages, this will easily flood their servers, They may ask for the patches we occasionally need to compile a package for LEAF. But those will be almost useless sitting alone in a tarball. We do have a build environment that we use to build our packages, it's available in cvs, but it's not released in FRS. And we do release a few scripts and files in FRS written or modified by LEAF developers like linuxrc, apkg... but these are shell scripts, which are their own source by nature. kp (btw: the issue started with DavidMBrookes question, if sources should go into cvs or not? The discussion drifted away - any ideas on that topic?) ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
