[MapProxy] Presumed libproj problem with my simple sample

André Pirard A.Pirard.Papou at gmail.com
Thu Nov 21 12:41:33 PST 2013

Hi Oliver,

Thanks for your reply.

On 2013-11-21 19:14, Oliver Tonnhofer wrote :
> Hi André,
> I do know the benefits of binary packages and I do understand that it would make live easier for some people. But you have to understand that people who work on open source projects mostly "scratch their own itches". I work hard to make MapProxy stable, robust, well tested and documented and with regular releases, but I cannot please everyone. There will always be people who have new ideas for 'must-have' features, people who need more documentation, people who want more tools - and that's ok. I encourage every one to help if they think there is a need for X, but they can't expect that X becomes an "itch" for me.
Be sure that I'm sure to speak on behalf of all Mapproxy users when
saying that they appreciate what you do very MUCH. Understand that some
of us support their non geek mates and really do without Python and with
a DEB. Recent Mila on this list is an example: one week to try to
install MP.
I'm always careful to suggest least work improvements (anti "please add
voice") and I even strive to overcome my ignorance to make small patches
like Arcgis TEST à la hack. You would be surprised why it's so important
for our OSM community.

> On 20.11.2013, at 23:49, André Pirard wrote:
>> I don't know how the DEBs have been generated, but it must be with a
>> command running in a matter of seconds. 
> It is a matter of seconds if you have a running Debian system and all
> dependencies. But it's not just calling a Makefile: you need to update
> the changelog, you might need to update patches, update dependencies,
> etc. Cool if the .deb for the LiveDVD worked on you system, but 
I know, I've tried but I was learning and I needed more MP info.
> Do you really want to autostart a developer server on a real server?
Autostart and shortcut are optional boons. You may start and use MP the
documentation way.
> you can't expect that all Debian and Ubuntu versions have the same
> dependencies. How would you handle that? 
The same as you did it for the DEBs you made.  DEB dependencies is doing
automatically what some people do manually. Normally, they are are the
same as what the documentation lists.

As I should cope with requirements and as, just like Java, Python
installation is a matter of copying files, I have good chances of making
a well working 1.6 DEB if somebody provides an image of his installed
files. Else, we'll be using 1.5.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20131121/514996d4/attachment.html>

More information about the MapProxy mailing list