Opened 12 years ago

Last modified 9 years ago

#35854 new submission

new port: py-pyccn (PyCCN - CCN bindings for Python)

Reported by: cawka (Alex Afanasyev) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: petrrr
Port: py-pyccn

Description

A "thin" implementation, which supports Python objects corresponding to the major CCNx entities - Interest, ContentObject, and so on, as well as some support objects. The C code is mostly just responsible for marshaling data back and forth between the formats, though there are some useful functions for key generation/access included.

Attachments (2)

Portfile (2.1 KB) - added by cawka (Alex Afanasyev) 12 years ago.
Portfile
Portfile.2 (2.1 KB) - added by raimue (Rainer Müller) 11 years ago.

Download all attachments as: .zip

Change History (6)

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

Cc: alexander.afanasyev@… removed
Keywords: ccnx python removed
Port: py-pyccn added

Some observations:

  • When you add "use_autoreconf yes", MacPorts automatically adds autoconf, automake and libtool build dependencies; you don't need to do it manually. When you add your own dependencies, use -append so that you don't overwrite these, or else ensure "use_autoreconf yes" appears after you've defined your dependencies. Usually we write the portfile more or less in chronological order, so directives like "use_configure yes" and "use_autoreconf yes" that affect the configure phase go near your other configure-phase directives (configure.args, configure.env).
  • The revision should start at 0 not 1.
  • You should use the github portgroup to simplify the port.
  • configure.args and configure.env should be set in the global part of the portfile, not in a pre-configure block, unless you're referring to variables that aren't set yet, but in this case it doesn't appear that way.
  • You can append multiple things to configure.env (and other options) at once; just list them one after the other; you don't have to call "configure.env-append" multiple times.
  • You can usually set configure.python, instead of manually appending PYTHON=... to the environment.
  • The portfile's indentation is a bit disorganized; it's usually preferable to keep the portfile in two columns where possible. Often we have the second column at 20 characters, but for python ports you might want to move it over to 24 characters since "python.default_version" is already 22 characters long.

comment:2 Changed 12 years ago by cawka (Alex Afanasyev)

Uploaded a corrected Portfile.

I tried originally to put configure.env-append in a global part, but I was getting an error message every time I tried to do portindex:

Failed to parse file net/py-pyccn/Portfile: can't read "python.pkgd": can't read "python.version": no such variable

Changed 12 years ago by cawka (Alex Afanasyev)

Attachment: Portfile added

Portfile

Changed 11 years ago by raimue (Rainer Müller)

Attachment: Portfile.2 added

comment:3 Changed 11 years ago by raimue (Rainer Müller)

Since this port uses subports, the build instructions should only be defined in a block for the subport.

comment:4 Changed 9 years ago by petrrr

Cc: petr@… added

Cc Me!

Note: See TracTickets for help on using tickets.