[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#138971: ITP Mapserver



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Aug 18, 2004, at 8:30 AM, C. Scott Ananian wrote:

On Wed, 18 Aug 2004, Robert Jordens wrote:

You participated in the discussion about packaging the UMN masperver for
Debian. Who of you is still interested in working of the package? What
are the problems?

I have packages, and am still using MapServer (so can test new ones).
The status is still as posted previously.  Packages at
    http://cscott.net/Debian/MapServer/
PHP/MapScript is still not included, although I might be a little bit more
motivated to try.
  --scott

I also have been maintaining a debian package for mapserver. I have not kept as up-to-date with the upstream releases as Scott has (I'm at 4.0.1) but hey isn't that the Debian way?

Add to your /etc/apt/sources.list if you want:

 deb http://www.paulbaker.net/debian stable main
 deb-src http://www.paulbaker.net/debian stable main

I should mention that I have built my package against Woody (by also backporting all of the dependencies, and whoa was that a lot of work). My package is also mentioned on the MapServer wiki: http://mapserver.gis.umn.edu/cgi-bin/wiki.pl?DebianLinux

I have broken mine out into three separate packages: mapserver-cgi, mapserver-utils, and libmapscript-perl. I have not attempted to build any of the other Mapscript language bindings.

My hope was to one day upload the package into Debian, but don't feel it is quite yet ready. The main things I see as show stoppers are:

 1. No manpages for any of the utils. Policy requires each to have
    a manpage. No upstream plan to provide these.
 2. Definitely would want to build a mapscript-php4 package.
    I have not spent much time trying to make this happen.
 3. Probably would also want to build a mapscript-python package.
 4. Finally, we may want to provide multiple flavours as of the package.
Mapserver can be compiled with A LOT of features, or very few features. But everything is pretty much either turned on or off at compile time.
    So do you build the package with everything compiled in? Or do you
    scale it back? Or do you provide multiple versions?

These are all things I wanted to sort out before wasting Debian's time with the package. But if there is a sponsor (you Robert) that is willing to help work through these issues, I have no problem wasting your time. :-)

- -- Paul Baker

"All whitespace is equivalent except in certain situations."
          -- Footnote 82, ANSI C

GPG Key: http://homepage.mac.com/pauljbaker/public.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFBI/V3oxmRVfL3nlsRAs4pAJ9ullLjtM2AUhuArV3vU6rH4ng5tgCeJ7T9
t3VagE8LBMeyjUJWcv0lHII=
=/fCb
-----END PGP SIGNATURE-----




Reply to: