Opened 8 years ago

Closed 8 years ago

#36493 closed submission (fixed)

voms-cli @2.0.7 New submission

Reported by: okoeroo@… Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc:
Port: voms

Description

This port will build and install Virtual Organisation Management Service (VOMS) tools. These tools play an important role in Grid Computing security usage for the end users.

The most significant build products are:

  • voms-proxy-init
  • voms-proxy-list
  • voms-proxy-info
  • libvomsapi.dylib

Attachments (5)

Portfile (947 bytes) - added by okoeroo@… 8 years ago.
Renewed VOMS CLI Portfile. Now using the GitHub repo directly.
Portfile.2 (1.1 KB) - added by okoeroo@… 8 years ago.
Portfile.3 (1.0 KB) - added by ryandesign (Ryan Schmidt) 8 years ago.
main.log (45.0 KB) - added by ryandesign (Ryan Schmidt) 8 years ago.
Portfile.4 (1.3 KB) - added by ryandesign (Ryan Schmidt) 8 years ago.

Download all attachments as: .zip

Change History (16)

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

Thanks. Could you explain why you're hosting the distfile on what looks like it might be your personal web site, instead of pulling it from github?

Since this software is hosted at github, the port should be using the github portgroup. Perhaps using the github portgroup will address the reasons why you didn't want to get the distfile from github.

The port you submitted is for version 2.0.7 but the current version on github is 2.0.8.

The license should be written "Apache-2".

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

Cc: ryandesign@… added

Cc Me!

comment:3 in reply to:  1 Changed 8 years ago by okoeroo@…

Replying to ryandesign@…:

Thanks. Could you explain why you're hosting the distfile on what looks like it might be your personal web site, instead of pulling it from github?

Since this software is hosted at github, the port should be using the github portgroup. Perhaps using the github portgroup will address the reasons why you didn't want to get the distfile from github.

The port you submitted is for version 2.0.7 but the current version on github is 2.0.8.

The license should be written "Apache-2".

The 2.0.7 is the version I'm successfully running on my laptop from a private build. I'm new to adding new MacPorts myself, so the intent was to migrate to the new 2.0.8 version after doing some testing on the OSX platform.

I'll change the Portfile to reflect the proper license statement and take the sources straight from Github.

Changed 8 years ago by okoeroo@…

Attachment: Portfile added

Renewed VOMS CLI Portfile. Now using the GitHub repo directly.

comment:4 in reply to:  1 Changed 8 years ago by okoeroo@…

Replying to ryandesign@…:

Thanks. Could you explain why you're hosting the distfile on what looks like it might be your personal web site, instead of pulling it from github?

Since this software is hosted at github, the port should be using the github portgroup. Perhaps using the github portgroup will address the reasons why you didn't want to get the distfile from github.

The port you submitted is for version 2.0.7 but the current version on github is 2.0.8.

The license should be written "Apache-2".

Hi,

I've applied all your comments in the new Portfile (same name, replaced the original attached file). In short:

  • using the GitHub repo with git
  • License statement updated
  • bumped version to the latest available git tag

The port nicely installs and uninstalls on my laptop from my local port repo.

comment:5 Changed 8 years ago by okoeroo@…

This could be too much information... but the attached voms-cli-2.0.7.tar.gz​ is obsoleted by the Git repo info in the Portfile.

Changed 8 years ago by okoeroo@…

Attachment: Portfile.2 added

comment:6 Changed 8 years ago by okoeroo@…

Added a renewed Portfile.

  • The Portfile.2 uses the github portgroup
  • Uses file hashes
  • Has been *renamed* from voms-cli to voms. This is to stay inline with the name used on the origin github, being 'voms'.
  • Replaced the autoreconf option with running the autogen.sh script (motivation: upstream might use a different contents in the future in the autogen.sh script)
  • Added build time dependencies to autotools
  • The pre-configure 'system' call is reduced to one command with an explicit working directory "system -W ${worksrcpath} ..."

comment:7 Changed 8 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… removed
Owner: changed from macports-tickets@… to ryandesign@…
Port: voms added
Status: newassigned

Thanks.

comment:8 Changed 8 years ago by ryandesign (Ryan Schmidt)

I'm attaching a revised Portfile in which I removed the name, revision and homepage lines (because the values you'd set were the defaults) and changed the version line to be computed from the github version. But the port doesn't build for me. I'm also attaching my main.log.

Changed 8 years ago by ryandesign (Ryan Schmidt)

Attachment: Portfile.3 added

Changed 8 years ago by ryandesign (Ryan Schmidt)

Attachment: main.log added

comment:9 Changed 8 years ago by okoeroo@…

I'll double check on my Mountain Lion system. My Snow Leopard makes this build cleanly. Thanks for the revisions.

comment:10 Changed 8 years ago by ryandesign (Ryan Schmidt)

I'm attaching a revised Portfile now using version 2.0.9. I've added a dependency on expat since it's listed in the project's requirements. I've added configure args to ensure MacPorts versions of expat and openssl are used. It doesn't change the error message I encounter on Mountain Lion. I see you've reported this as upstream issue 1.

I also tried building on Leopard. First I encountered a problem because I had mongodb installed, which installs ${prefix}/include/server.h, and this got used instead of the Server.h included in the voms package, because I have a case-insensitive filesystem, and the project lists flags in the wrong order resulting in -I${prefix}/include appearing before local project directories. I fixed this by changing the -I${prefix}/include which MacPorts automatically adds to -isystem${prefix}/include, since -isystem directives always come after all -I directives.

But even after that, the build fails on Leopard with this error:

ipv6sock.cc:51: error: 'EAI_OVERFLOW' was not declared in this scope
ipv6sock.cc:74: error: 'EAI_OVERFLOW' was not declared in this scope

Changed 8 years ago by ryandesign (Ryan Schmidt)

Attachment: Portfile.4 added

comment:11 in reply to:  10 Changed 8 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: assignedclosed

Replying to ryandesign@…:

But even after that, the build fails on Leopard with this error:

ipv6sock.cc:51: error: 'EAI_OVERFLOW' was not declared in this scope
ipv6sock.cc:74: error: 'EAI_OVERFLOW' was not declared in this scope

I have filed upstream issue 2 for this.

Since the port does build on Snow Leopard, I have committed it in r99367.

The test suite appears to require a program called "runtest" which is provided by the dejagnu port, so I added a check for that to the port before committing it. There still remain several problems preventing the test suite from running properly, but I'll file additional upstream and/or MacPorts bug reports about that.

Note: See TracTickets for help on using tickets.