| 1 | # $Id$ |
|---|
| 2 | |
|---|
| 3 | PortSystem 1.0 |
|---|
| 4 | PortGroup python25 1.0 |
|---|
| 5 | |
|---|
| 6 | name protobuf-py |
|---|
| 7 | version 2.0.3 |
|---|
| 8 | categories-append devel |
|---|
| 9 | maintainers nomaintainer |
|---|
| 10 | description Encode data in an efficient yet extensible format. |
|---|
| 11 | |
|---|
| 12 | long_description \ |
|---|
| 13 | Google Protocol Buffers are a flexible, efficient, \ |
|---|
| 14 | automated mechanism for serializing structured data -- \ |
|---|
| 15 | think XML, but smaller, faster, and simpler. You \ |
|---|
| 16 | define how you want your data to be structured once, \ |
|---|
| 17 | then you can use special generated source code to \ |
|---|
| 18 | easily write and read your structured data to and from \ |
|---|
| 19 | a variety of data streams and using a variety of \ |
|---|
| 20 | languages. You can even update your data structure \ |
|---|
| 21 | without breaking deployed programs that are compiled \ |
|---|
| 22 | against the "old" format. You specify how you want \ |
|---|
| 23 | the information you're serializing to be structured by \ |
|---|
| 24 | defining protocol buffer message types in .proto \ |
|---|
| 25 | files. Each protocol buffer message is a small \ |
|---|
| 26 | logical record of information, containing a series of \ |
|---|
| 27 | name-value pairs. |
|---|
| 28 | |
|---|
| 29 | homepage http://code.google.com/p/protobuf/ |
|---|
| 30 | master_sites googlecode:protobuf |
|---|
| 31 | |
|---|
| 32 | distname protobuf-${version} |
|---|
| 33 | use_bzip2 yes |
|---|
| 34 | checksums md5 37e6e4d63434672c70bd977be9c372cb \ |
|---|
| 35 | sha1 aad5cbe1423060b0ff315d2a1447e7bf1209dc63 \ |
|---|
| 36 | rmd160 624ea3075ba5756106c367be224c6eb68ee4ae69 |
|---|
| 37 | |
|---|
| 38 | platforms darwin |
|---|
| 39 | |
|---|
| 40 | depends_lib port:protobuf-cpp \ |
|---|
| 41 | port:py25-setuptools |
|---|
| 42 | |
|---|
| 43 | worksrcdir ${worksrcdir}/python |
|---|
