> > Urr...
> > Spot a suspicious ..
> > % cd ~/work/thousandparsec/tpserver-cpp/tpserver
> > % ./tpserver-cpp
> >
> > Nothing....
>
> Yes, nothing. If you had read the README file (or the updated getting
> started
> page) you would have seen that tpserver-cpp uses a config file.
Reading the README in there document, and the fact the program starts up
without a config file without an error still tell me the config file is
optional.
Additionally the defaults in the supplied config file need to be
modified anyway.
Really my point is: Documented or not, it would be really nice if the
server would "just work" out of the box. From the ones in darcs/cvs not
being in a working state is fine. For the release version - it really
should be a good state to just go.
> I have just added a few defaults for when someone runs tpserver-cpp without
> any command line arguments. Still doesn't get it on the network though.
If a "network start" is all that is required... all good.
> I am also providing two config files for the AI Competition in a few days
> time.
Weren't there when I downloaded it...
>
> There is a good chance that nmap would not map the ports tpserver-cpp uses.
To be precise I used:
nmap -p 6000-7000 localhost
Remember it screwed up the python server...
> Well, it tries /etc/tpserver.conf or the one provided on the command line. I
> have two local config files and I change between them to test things. The
> sample.conf file doesn't do anything, it's all commented out.
Which is annoying. For the release, it would be nice to a have pretty
standard sane server conf. At this point people just want to have a
quick go, see what the client and server are like. Playing round with a
config file is not what I wanted to do at that point.
> I know of the open issues around the console. A prompt will be put in once I
> get it sorted.
>
> I also intend to add a "wizard" or setup guide on the console when it detects
> no configuration (namely when a ruleset is not loaded). This is a big tasked
> and will not be completed soon. I may add a "status" message on the console
> to give a clue about what the user has to do next.
Short term solution next release should ship with a basic usuable config
file.
> I have updated it to help people a bit. Running a server is not for everyone.
I was unable to connect to any other server at the time. What other
alternative was there?
> > Not quite... At that point I have a window open, and I need to figure
> > out how to connect to a server. I personally could not get it to
> > connect to the main servers (the second test server didn't resolve at
> > the time). Hence I found my next step was to set up a server.
>
> demo1.thousandparsec.net is almost always running. If you have problems
> logging in, try a different username and password. demo1 has autoadd_players
> on.
Tried multiple users and multiple passwords. Not sure of the format of
user names (the example has @tp - is that required)?
> > But as I said, it's a PITA, and autoconf doesn't make it easy. I was
> > impressed that inkscape does this in the build for the things it tests
> > with pkg-config (gtkmm and friends)
>
> I use pkg-config for a few things, as libraries slowly change over to them. I
> am still working on separating the libraries as some are only needed for one
> module, but are linked in server-wide.
It is a minor concern.
> > Once set up it all seems good.
>
> Cool. I hope the updated getting started page helps.
Won't know until someone else new gives it a try, and takes the time to
provide feedback.
> > Even better would be if one server could run multiple games with
> > different rule sets....
>
> Apparently the python server can. tpserver-cpp will not, just too complex.
:-(
> wrt: Darcs
> > [2] As a semi-aside, getting the joy of using another RCS isn't a great
> > thing, especially as the darcs home page is pretty poor for info - until
> > you use google to search it... Not sure you guys can fix that however.
>
> Blame me for that one. Darcs is nice, and as a scientist, I do understand it.
> I had been playing with it for some of my own projects. If we were to move
> RCS again, I would probably suggest Mercural (hg).
To be fair it's a minor thing. 5 years ago everything was on CVS -
simple, everyone knew it. Now we have more popular RCSs then I would
have believed possible... Git, Arch, Baz, Bzr, Hg, Darcs, SVN...
It's hard to make a good choice for everyone. So pick the one you have
a local guru for ;-)
Regards,
nash
_______________________________________________
tp-devel mailing list
[email protected]
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
