Port for MapServer

[mbarchfe@…]

Attached you find a Portfile for MapServer. I would suggest to categorize it and its dependencies as gis.

[mbarchfe@…]

Portfile for MapServer

[ryandesign@…]

Thanks for the contribution!

port lint has the following suggestions about your Portfile:

$ port lint
--->  Verifying Portfile for mapserver
Warning: Line 2 should be a newline (after RCS tag)
Warning: Line 3 should be a newline (after PortSystem)
Warning: Line 21 has trailing whitespace before newline
Warning: Line 33 has trailing whitespace before newline
Warning: Line 35 has trailing whitespace before newline
Warning: Line 36 has trailing whitespace before newline
Warning: Line 37 has trailing whitespace before newline
Warning: Line 38 has trailing whitespace before newline
Warning: Line 40 has trailing whitespace before newline
Warning: Line 41 has trailing whitespace before newline
Warning: Line 42 has trailing whitespace before newline
Warning: Line 43 has trailing whitespace before newline
Error: Unknown category: gis
Warning: Variant gdalogr does not have a description
Warning: Variant proj does not have a description
Warning: Variant wms does not have a description

The whitespace notices aren't so important and will probably be removed from port lint anyway, but the others are relevant. Variants should have descriptions explaining their use, and we don't have a category "gis". Perhaps the port would fit into one of the existing categories.

Further comments from me:

• You don't wish to be the maintainer of this port?
• It looks like the variant "wms" doesn't do anything so it should be removed.
• In the destroot phase you should use xinstall instead of system "install".
• With regard to your comment on setting the cgi_path, this project is called MacPorts. It hasn't been called DarwinPorts in 16 months. :-)
• extract.suffix .tar.gz is unnecessary; that's the default.

[mbarchfe@…]

tidied up version (except for category)

[mbarchfe@…]

port lint has the following suggestions about your Portfile:

sorry, should have run that beforehand. Attached is a cleaned file.

The whitespace notices aren't so important and will probably be removed from port lint anyway, but the others are relevant. Variants should have descriptions explaining their use, and we don't have a category "gis". Perhaps the port would fit into one of the existing categories.

Where can I find out about valid categories? According to http://www.macports.org/ports.php ther is a gis category.

Further comments from me: * You don't wish to be the maintainer of this port?

Actually I hoped I could throw this over the fence and get away with it ;-). But if being the maintainer means I can directly submit changes to the Portfile that would be fine with me.

* It looks like the variant "wms" doesn't do anything so it should be removed.

It adds a necessary dependency for wms. I wanted this category just to make it explicit.

* In the destroot phase you should use xinstall instead of system "install".

Fixed.

* With regard to your comment on setting the cgi_path, this project is called MacPorts. It hasn't been called DarwinPorts in 16 months. :-)

Sorry, I am new to Mac and this does not mean much to me.

* extract.suffix .tar.gz is unnecessary; that's the default.

Removed.

[mbarchfe@…]

Port for mapserver, grass and gdal grass plugin

[mbarchfe@…]

The new attachment gis.tar.gz contains some improvements for mapserver plus ports for grass and the grass plugin for gdal. With these ports it is possible to develop with grass and directly access grass data from mapserver.

The mapserver port has got a patch for Makefile.in to support DESTROOT.

[mbarchfe@…]

Sorry, I meant DESTDIR instead of DESTROOT.

[ryandesign@…]

Replying to mbarchfe@googlemail.com:

we don't have a category "gis". Perhaps the port would fit into one of the existing categories.

Where can I find out about valid categories? According to http://www.macports.org/ports.php ther is a gis category.

Oh, I see, indeed ports.php does show a gis category. I was going by "port lint" which said the category didn't exist. lint currently goes off a list that's in portlint.tcl, while I believe ports.php gathers all categories of all ports and displays them. Looks like only the spatialite port currently claims to be in category gis. Would the science category be appropriate? That's where ports like gdal, geos and proj are currently filed. Or if it would help people to find the software if the ports were in a category gis, we could officially add that category. Ports can be in multiple categories; e.g. you could file them in science and gis.

* You don't wish to be the maintainer of this port?

Actually I hoped I could throw this over the fence and get away with it ;-). But if being the maintainer means I can directly submit changes to the Portfile that would be fine with me.

You don't need to be maintainer if you don't want to. :-) The problem is that ports with no mainatiner seem to bitrot as nobody feels responsible for them, and already 46% of our ports have no maintainer. By being a port's maintainer, you're saying that you will keep it updated and be a point of contact for users having questions about the MacPorts-specific aspects of the software. You would still need to file tickets to effect those updates, unless you want to  request commit access to the repository.

* It looks like the variant "wms" doesn't do anything so it should be removed.

It adds a necessary dependency for wms. I wanted this category just to make it explicit.

But the wms variant doesn't do anything. It only contains the comment "--with-wms is enabled by default". The description of the variant reads "Enable Web Map Service" but that's not what the variant does. Regardless of whether I install mapserver +proj or mapserver +proj +wms I get exactly the same software which has wms enabled. So the wms variant should go away. If there is value in allowing wms to be disabled, then you could add a variant no_wms which appends the configure argument --without-wms. Is there a reason why anyone would want to disable wms?

[mbarchfe@…]

we don't have a category "gis". Perhaps the port would fit into one of the existing categories.

Where can I find out about valid categories? According to http://www.macports.org/ports.php ther is a gis category.

Oh, I see, indeed ports.php does show a gis category. I was going by "port lint" which said the category didn't exist. lint currently goes off a list that's in portlint.tcl, while I believe ports.php gathers all categories of all ports and displays them. Looks like only the spatialite port currently claims to be in category gis. Would the science category be appropriate? That's where ports like gdal, geos and proj are currently filed. Or if it would help people to find the software if the ports were in a category gis, we could officially add that category. Ports can be in multiple categories; e.g. you could file them in science and gis.

I think it would make sense to add the gis category. gdal/geos/proj/grass/mapserver/gdal-grass should probably be tagged for the science and gis category.

* You don't wish to be the maintainer of this port?

Actually I hoped I could throw this over the fence and get away with it ;-). But if being the maintainer means I can directly submit changes to the Portfile that would be fine with me.

You don't need to be maintainer if you don't want to. :-) The problem is that ports with no mainatiner seem to bitrot as nobody feels responsible for them, and already 46% of our ports have no maintainer. By being a port's maintainer, you're saying that you will keep it updated and be a point of contact for users having questions about the MacPorts-specific aspects of the software. You would still need to file tickets to effect those updates, unless you want to  request commit access to the repository.

Then I would suggest that you enter my email address as maintainer and add the ports to the repository. I will then request access to the repository.

* It looks like the variant "wms" doesn't do anything so it should be removed.

It adds a necessary dependency for wms. I wanted this category just to make it explicit.

But the wms variant doesn't do anything. It only contains the comment "--with-wms is enabled by default". The description of the variant reads "Enable Web Map Service" but that's not what the variant does. Regardless of whether I install mapserver +proj or mapserver +proj +wms I get exactly the same software which has wms enabled. So the wms variant should go away. If there is value in allowing wms to be disabled, then you could add a variant no_wms which appends the configure argument --without-wms. Is there a reason why anyone would want to disable wms?

No, but wms depends on proj and if somebody wanted to enable wms (s)he would have to add the proj variant. --with-wms is given per default but will only be considered if there is proj support as well. Since I did not regard this as intuitive I have added the wms variant. As an alternative the proj variant could be renamed to wmsproj or so.

[macsforever2000@…]

mapserver port added in r41898 and modified in r41899. Hopefully I satisfied all parties. :)

[macsforever2000@…]

Cc Me!

[macsforever2000@…]

I could use a suggestion about the grass port. Currently it violates the mtree and it seems something better should be done for that. Attaching my mods to the portfile.

[blb@…]

Attaching a tarball with my attempt for grass. It builds the unix-style grass, not the Mac app, as the Mac app it built here properly installs into the destroot but is missing the Info.plist file that Mac OS X expects and therefore doesn't run. Also enabled parallel builds as it built fine several times with it enabled.

[blb@…]

grass port

[macsforever2000@…]

My latest version of the grass portfile based on blb's changes. Fixed variants. Fixed dependencies.

[macsforever2000@…]

grass added r42393.

[macsforever2000@…]

I'm not able to get gdal-grass to install. Here's my modified version of the portfile. Any ideas would be appreciated!

[anonymous]

Milestone Port Submissions deleted