#16770: protobuf-cpp-2.0.2 (upgrade from 2.0.1) ---------------------------------+------------------------------------------ Reporter: stromnov@gmail.com | Owner: blair@macports.or Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: | Keywords: Port: protobuf-cpp | ---------------------------------+------------------------------------------ Changes (by macsforever2000@macports.org): * owner: macports-tickets@lists.macosforge.org => blair@macports.or Comment: Assigning to maintainer. -- Ticket URL: <http://trac.macports.org/ticket/16770#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#16770: protobuf-cpp-2.0.2 (upgrade from 2.0.1) ---------------------------------+------------------------------------------ Reporter: stromnov@gmail.com | Owner: blair@macports.org Type: enhancement | Status: closed Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: fixed | Keywords: Port: protobuf-cpp | ---------------------------------+------------------------------------------ Changes (by blair@macports.org): * status: new => closed * resolution: => fixed Comment: Thanks for the patch. Upgraded to 2.0.2 in r40541. However, I don't think we need the py25 variants work, so I left that out. From my experience, the protoc generated Python files are always imported into another script which can specify the Python version to use at the top of the file. If you need Python support, you could write a protobuf-py and protobuf-py25 module that would install the Python protobuf files into Python 2.4 and 2.5 and I could check that into svn. Closing as fixed, feel free to comment on this and we'll reopen the ticket if something else needs to be done to the port. -- Ticket URL: <http://trac.macports.org/ticket/16770#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS