Le 27/03/2013 19:13, Pieren a écrit :
On Wed, Mar 27, 2013 at 6:33 PM, Andy Allan <[email protected]> wrote:
So think twice before telling a new user that they should start
editing wiki pages.
Instead of 'new user', I would say 'the end users, those from whom the
documentation is intended'. Since the devs do not take a high priority
to keep the wiki up-to-date and consistent (sigh), anybody else taking
the time to search, read the docs with new eyes, follow the process,
find and fix issues for himself, etc is able to improve the doc for
the next ones.
I said "improve the doc", not "write another 'how-to setup my own tile server'".
Pieren
_______________________________________________
No problem with Pieren's message, I know how painful it is when you work
all day on something and a newcomer complains because of a free lunch
not included yet.
Anyway I'm close to finish an ansible playbook to setup a VM just
installed with the core F18 packages, to have a working tile server +
nominatim. I choose ansible because it is extremely easy to setup and
requires no server in the system being targeted, but sshd and to have
setup ~/.ssh/authorized_keys. It seems a reasonable approach to list
exhaustively every step that must be done.
Of course this playbook needs to be checked by people knowing the
different OSM components, I probably have done very stupid things and I
also use ansible for a few days and didn't take time to make the
playbook a very nice one (for instance I had problems understanding
symlinks handling so I just remove them and 'ln -fs' them afterwards).
So much to do and not much time available so I have to follow an
aggressive approach about everything these days :-)
Bu there is the problem of copying files (.tgz/conf/.sh/etc.) that I
built during the process. For instance for Tirex I applied such a patch:
Index: backend-mapnik/Makefile
===================================================================
--- backend-mapnik/Makefile (revision 29404)
+++ backend-mapnik/Makefile (working copy)
@@ -1,7 +1,7 @@
INSTALLOPTS=-g root -o root
CFLAGS += -Wall -Wextra -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
CXXFLAGS = $(CFLAGS) `mapnik-config --cflags`
-LDFLAGS= `mapnik-config --libs --ldflags --dep-libs`
+LDFLAGS= `mapnik-config --libs --ldflags --dep-libs| sed -e s/-l.agg.//`
backend-mapnik: renderd.o metatilehandler.o networklistener.o networkmessage.o networkrequest.o networkresponse.o debuggable.o requesthandler.o
$(CXX) -o $@ $^ $(LDFLAGS)
Index: backend-mapnik/metatilehandler.cc
===================================================================
--- backend-mapnik/metatilehandler.cc (revision 29404)
+++ backend-mapnik/metatilehandler.cc (working copy)
@@ -23,7 +23,7 @@
#include <mapnik/datasource_cache.hpp>
#include <mapnik/font_engine_freetype.hpp>
#include <mapnik/agg_renderer.hpp>
-#include <mapnik/expression.hpp>
+//#include <mapnik/expression.hpp>
#include <mapnik/image_util.hpp>
#include <mapnik/load_map.hpp>
#include <mapnik/box2d.hpp>
So for Tirex I made up a .tgz of the revision I got including this
patch, and have ansible to copy it to the target and recompile it
locally. I also copy mapnik fonts, there still a few 'wget svn..' (with
no revision number ;-)), etc: this is purely an approach to reach a
working system and to avoid digging into the details to make it a
perfect one.
Bernard
_______________________________________________
dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/dev