> There better could be different TORELEASE files. As for Jaluino, it has its > own SVN and own release cycle w/ TORELEASE.
There could also be 2 or more buildbot's as well so JAT can check if files in TORELEASE compile ok. We could then change the name of the release package to "Jallib-JalV2-pack", and also have a Jallib-JAT- pack, and for mike a "Jallib-JalV3-pack". The issue I have is that I don't want to see many branches of libraries. All of these three "packs" could release the same libraries and some additional libraries, but can contain a different compiler. Some compilers may have more or less features then others. I do not like the fact that Jaluino uses a different set of libs because those libs could become outdated (although seb may disagree), I have not used Jaluino libs so I would not know. Does Jaluino contain the same Jallib libraries if/when a library is updated? How do you insure that the library is always the same? I would rather keep Jaluino libs here, although it's discussion could be elsewhere. Jaluino to me is Hardware, not software. Are the Jaluino libs not accepted by Jallib? Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
