[MacPorts] #26040: New port: xymon
MacPorts
noreply at macports.org
Mon Aug 16 03:04:14 PDT 2010
#26040: New port: xymon
-----------------------------+----------------------------------------------
Reporter: fclaire@… | Owner: macports-tickets@…
Type: submission | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Keywords: | Port: xymon
-----------------------------+----------------------------------------------
Changes (by ryandesign@…):
* port: => xymon
Comment:
I have not spent a lot of time evaluating this, but my initial impressions
are
* this looks exceptionally complicated
* the server and client variants would seem to be totally conflicting
with one another, and should therefore so indicate, however wouldn't it
make a lot more sense to have two separate ports, one for the client and
one for the server? call the client port "xymon" and call the server
"xymon-server"; this matches how we handle postgresql and mysql now
* master_sites can just be "sourceforge"
* the first revision of any port version should usually be 0, not 1; you
can just omit the revision line entirely to accomplish that
* why use a beta version, and not a stable version?
* you must not "file mkdir" in the main part of a port; that would get
executed even on such operations as "port info"; you probably want the
destroot.keepdirs command in this case
* it's usually simplest to use "ln -s" instead of "file link -symbolic"
or "system 'ln -s'" to create symlinks; there are some cases where this
won't work; if this is one of those cases, please add a comment in the
portfile explaining it so others don't wonder
* we prefer to use notes now, instead of manually calling ui_msg in post-
activate
* you shouldn't hardcode /opt/local, not even in messages printed to the
user; use ${prefix}
--
Ticket URL: <http://trac.macports.org/ticket/26040#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list