On Mon, 2007-07-02 at 01:28 +0200, Aaron Kaplan wrote:
> On Jun 30, 2007, at 11:48 PM, Bernd Petrovitsch wrote:
> > On Thu, 2007-04-05 at 20:33 +0200, Immo 'FaUl' Wehrenberg wrote:
> > [...]
> >> forward to apply it by tomorrow with minor changes into
> >> the svn://dev.durchdieluft.net/olsr-quagga/trunk/quagga/
> >> repository.
> >
> > Is the version there working (and I can thus put it into
> > olsrd-CVS-HEAD)?
> 
> please test first in a live system!

Well, that's the usual problems with most plugins, that one needs a test
setup and some basic/simple "how to test it" information.
And for most of them, I don't even know test scenarios (and I'm not
asking for full blown regression test suites, just simple test to learn
a little about the plugin) so perhaps people can add them to the plugins
(if not done already - I haven't checked all of them).

And I expect submitted patches to have been used/testes by the
submitters so they should work in theory.

I can easily compile and load the plugins but that doesn't say much
IMHO. OK, I can easily test txtinfo and httpinfo but for e.g. quagga one
needs probably more to get a somewhat working test setup..

The other question for plugins that have their own CVS/SVN/... is: Does
it make sense to copy them in the OLSR-CVS? Or isn't it better to have
some code in the appropriate place which knows how to check out that
plugin and make it look like a local one.
And what should be done for releases as .tar.gz?

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services




