PlaneShift
Development => Development Deliberation => Topic started by: Thaodan on November 20, 2012, 08:49:05 pm
-
I'm planing to build a (client) package for the offical servers, but how get the client that fits to the offical servers?
-
iirc #planeshift-build on freenode.net would be the best first hop.
but there is some direction including build guides here: http://planeshift.svn.sourceforge.net/viewvc/planeshift/trunk/docs/compiling.html
-
but there is some direction including build guides here: http://planeshift.svn.sourceforge.net/viewvc/planeshift/trunk/docs/compiling.html
I lookedat that but there's nothing about getting the version that fits to the offical servers.
-
crystalspace trunk head and planeshift trunk head work most of the time with official server using the art from released client.
-
Ok, but for building packages a stable version that is released in specific times woud be much better, even when the package will be moved too the community reposity a vcs version woud be worse.
-
In the past it was announced in #planeshift-build which SVN release corresponds to the current stable client. No idea if that is still the case. And usually you really don't want to just use that release anyway. Simple errors are often fixed withing some weeks in the sources but it can take months until a new release of PS is made public. No real point in building your own client if you don't take advantage of the bugfixes. For packages I think I would try to version them by SVN versions and throw out packages a lot more often then official PS clients.