Ok. I guess I will keep with the current tree. One of the problems I see in future is that some of the modules will be *very* large, and people might object to downloading large amounts of code they will not use.
Another issue is that I will need to fix the CPPFLAGS and LDFLAGS I use internally to reduce extra linking and useless flags. So if someone wants to give me a hand with this I would be most grateful. Yet another is making sure that every module installs correctly and that the core correct installs headers, etc to allow out-of-tree development. This shouldn't be too hard as I think I have it ok already. I would like to point out that until recently, only one tarball was needed to build tpserver-cpp. It is now two with libtprl, but I hope that it will get used in other places as well (tpclient-cpptext is the most likely). More comments inline below. Later Lee On Thursday 29 June 2006 23:24, Tim Ansell wrote: > On Wed, 2006-06-28 at 23:40 +1200, Lee Begg wrote: > > Hi > > > > I have developed tpserver-cpp so that it now dynamically loads rulesets, > > persistence and tpscheme modules. The next step take the current modules > > out of the tpserver-cpp tree and into their own. > > I think this is a bad idea. > > Separating the modules for packaging is a good idea, IE > > tpserver-cpp-core_1.0.2-3_i386.deb > tpserver-cpp-ruleset-minisec_1.0.2-3_i386.deb > tpserver-cpp-tpscheme-mzscheme_1.0.2-3_i386.deb > tpserver-cpp-tpscheme-guile_1.0.2-3_i386.deb > tpserver-cpp-persistence-mysql_1.0.2-3_i386.deb > > The apt/yum/whatever will automagically get the recommended versions of > the modules. Yeah. > However when building from source, downloading 4 separate packages is a > bad annoying. > > Without the modules the server is pretty much useless. Without the > server the modules are useless. They are clearly not separate entities > and hence they should come together. I expect at least some modules will get developed out of tree. I think this will definitely become an issue once I hit a stable version (ie, 1.0.0) when most of the development will shift to modules. Until then, I will keep with the status quo. <snip> > One of the biggest criticism I have gotten is that there are too many > modules, making more is not a good idea. A quick count shows 19 darcs repos. 5 protocol libraries (that don't depend on each other). 1 client support library. 6 clients. 2 servers. 1 AI serverclient. 1 website 1 media archive 1 cpp support library 1 scratchpad. It takes two repos to make a server. It takes two to four repos to make a client. Not as bad as WF. <snip> > > Future plans: > > - Split modules out of tpserver-cpp tree > > - MTSec ruleset > > - Console improvements > > - http tunnel socket > > - fix wrong share dir for tpscheme impls > > - better universe generation > > All these look pretty good (apart from the split bit). Cool. Not sure about the exact order yet, the wrong share dir might get fixed real soon. > > Later > > Lee Begg
pgpZlXkvNEilG.pgp
Description: PGP signature
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
