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