Opened 13 years ago

Closed 22 months ago

#28187 closed submission (fixed)

simplevoc-open @1.7.0 submission ticket

Reported by: w.helisch@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc: k.salewski@…, f.celler@…, ryandesign (Ryan Schmidt)
Port: simplevoc-open php5-simplevoc


SimpleVoc-OPEN is an in-memory key/value store with a REST interface and some unique features. Beside Linux it also supports MAC OS. Details on the feature set are available here: Source Code can be downloaded here: Documentation is available here: Of course we would also do the maintenance of the packages at MacPorts. The identity should be: simplevoc-open. Real e-mail address should be: support@… Probably it's one of the few products of its kind that is also available for MAC OS. Hence it might be very interesting to Mac-Users.

Attachments (4)

Portfile (6.0 KB) - added by ryandesign (Ryan Schmidt) 13 years ago.
Portfile Wolfgang Helisch emailed to me and asked me to attach
php.php5-simplevoc.Portfile (1.3 KB) - added by w.helisch@… 13 years ago.
simplevoc php5extension portfile
database.simplevoc-open.2.Portfile (3.3 KB) - added by w.helisch@… 13 years ago.
simplevoc-open Portfile
database.simplevoc-open.Portfile (3.3 KB) - added by w.helisch@… 13 years ago.
simplevoc-open Portfile

Download all attachments as: .zip

Change History (12)

comment:1 Changed 13 years ago by ryandesign (Ryan Schmidt)

Port: simplevoc-open added

Changed 13 years ago by ryandesign (Ryan Schmidt)

Attachment: Portfile added

Portfile Wolfgang Helisch emailed to me and asked me to attach

comment:2 Changed 13 years ago by ryandesign (Ryan Schmidt)

Some thoughts on the portfile:

  • In the post-destroot, you can dispense with creating ${destroot}${prefix}/etc and ${destroot}${prefix}/sbin; MacPorts has already created them for you.
  • "xinstall -d" can accept multiple directory paths per invocation.
  • "xinstall" can install many files from a single directory in a single invocation (using the "-W" switch).
  • Instead of "eval xinstall ... [glob .../*.*]" why not just "copy"?
  • Mac OS X does not use a directory called "lib64"; all libraries, regardless of architecture (and often of multiple architectures simultaneously, i.e. universal binaries), are in "lib".
  • You are installing a PHP module; it might be better to do this in a separate port, using the php5extension portgroup; see any of the existing portfiles in the php category. You're also not declaring a dependency on php5, but if you make a separate port using the php5extension portgroup, that detail will be taken care of for you.
  • You are modifying the php.ini. Usually in MacPorts we leave conf files for the user to modify, and do not modify them for the user. And in this case, all you're doing is adding a line to load the extension. In the php5extension portgroup, we create a separate .ini file for each extension with that kind of statement in it. And again the portgroup will do it for you.
  • You're installing some conf files. Their names should probably not be *.conf but instead *.conf.sample, so that a user can then copy the *.conf.sample file to *.conf and edit it. Otherwise, MacPorts would register the *.conf file to the port, and overwrite it at the next port upgrade, wiping out any customizations the user made. Some ports that deal with this situation just tell the user (using a "notes" statement) what file to copy where, while others do so for the user (in the post-activate phase), if there isn't already a conf file there.
  • You're installing your own launchd plist, then using the startupitem keywords to create a MacPorts launchd plist, whose sole purpose is to call launchctl and load your plist? No; let's just dispense entirely with the MacPorts startupitem stuff and just let the user use your custom plist directly. Possibly you may want to rename it to org.macports.${name}.plist, or not. We don't have many ports providing their own non-MacPorts plists, but you may want to see how they do it. avahi comes to mind, and it looks like they do not rename it.
  • You've listed the supported architectures as i686 and x86_64. i686 is not a valid Mac OS X architecture. The only valid architectures are i386, x86_64, ppc and ppc64. You are certain this software does not work on PowerPC computers?

Changed 13 years ago by w.helisch@…

Attachment: php.php5-simplevoc.Portfile added

simplevoc php5extension portfile

Changed 13 years ago by w.helisch@…

simplevoc-open Portfile

comment:3 Changed 13 years ago by w.helisch@…

Modified according to Ryan Schmidt's remarks. Added php5extension group portfile.

SimpleVoc-OPEN should not run on ppc and ppc64 architectures due to internal memory handling.

Attachment "database.simplevoc-open.2.Portfile" should be deleted (upload error, didn't see replace button). Can anyone help?

Changed 13 years ago by w.helisch@…

simplevoc-open Portfile

comment:4 Changed 13 years ago by w.helisch@…

Modifications in attachment "database.simplevoc-open.Portfile":

  • New category: "databases" instead of "database".
  • Added target "touch" to build targets: now "touch" and "all".

comment:5 Changed 13 years ago by w.helisch@…

Dear Ladies or Sirs,

we try to process this ticket but there seems to be no progress for more than 10 days.

Is there anything we can do to push this forward?

Best Regards,


comment:6 Changed 13 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added

Thanks for making the changes. I've added simplevoc-open in r76462. I haven't looked at the php5 extension yet.

comment:7 Changed 12 years ago by jmroot (Joshua Root)

Port: php5-simplevoc added

Ryan, are you still planning to review php5-simplevoc?

comment:8 Changed 22 months ago by chrstphrchvz (Christopher Chavez)

Resolution: fixed
Status: newclosed

In 70e009295f9a0ccb4875080e1956a7be0cf772f7/macports-ports (master):

simplevoc-open: delete abandoned port

No point in keeping the port and designating it nomaintainer:
upstream project is gone, port is not known to build, no dependents.

Closes: #28187
See: #63136
Closes: #63986

Note: See TracTickets for help on using tickets.