Ticket #17537: Portfile.diff

File Portfile.diff, 3.5 KB (added by stromnov (Andrey Stromnov), 16 years ago)
  • Portfile

    old new  
    22
    33PortSystem 1.0
    44
    5 name            protobuf-cpp
    6 version         2.0.2
    7 categories      devel
    8 maintainers     blair
    9 description     Encode data in an efficient yet extensible format.
    10 
     5name            protobuf-cpp
     6version         2.0.3
     7categories      devel
     8maintainers     blair
     9description     Encode data in an efficient yet extensible format.
     10           
    1111long_description \
    12                 Google Protocol Buffers are a flexible, efficient, \
    13                 automated mechanism for serializing structured data -- \
    14                 think XML, but smaller, faster, and simpler.  You \
    15                 define how you want your data to be structured once, \
    16                 then you can use special generated source code to \
    17                 easily write and read your structured data to and from \
    18                 a variety of data streams and using a variety of \
    19                 languages.  You can even update your data structure \
    20                 without breaking deployed programs that are compiled \
    21                 against the "old" format.  You specify how you want \
    22                 the information you're serializing to be structured by \
    23                 defining protocol buffer message types in .proto \
    24                 files.  Each protocol buffer message is a small \
    25                 logical record of information, containing a series of \
    26                 name-value pairs.
    27 
    28 homepage        http://code.google.com/p/protobuf/
    29 master_sites    googlecode:protobuf
    30 
    31 distname        protobuf-${version}
    32 use_bzip2       yes
    33 checksums       md5 6674270b1d63c2c4b292644f48fede4e \
    34                 sha1 b3ebd8895000bb11ded88b1f207cb799653befa0 \
    35                 rmd160 bd76eeef45342a44b80a5bbf38ee28ccec021eea
     12                Google Protocol Buffers are a flexible, efficient, \
     13                automated mechanism for serializing structured data -- \
     14                think XML, but smaller, faster, and simpler.  You \
     15                define how you want your data to be structured once, \
     16                then you can use special generated source code to \
     17                easily write and read your structured data to and from \
     18                a variety of data streams and using a variety of \
     19                languages.  You can even update your data structure \
     20                without breaking deployed programs that are compiled \
     21                against the "old" format.  You specify how you want \
     22                the information you're serializing to be structured by \
     23                defining protocol buffer message types in .proto \
     24                files.  Each protocol buffer message is a small \
     25                logical record of information, containing a series of \
     26                name-value pairs.
     27
     28homepage        http://code.google.com/p/protobuf/
     29master_sites    googlecode:protobuf
     30
     31distname        protobuf-${version}
     32use_bzip2       yes
     33checksums       md5 37e6e4d63434672c70bd977be9c372cb \
     34                sha1 aad5cbe1423060b0ff315d2a1447e7bf1209dc63 \
     35                rmd160 624ea3075ba5756106c367be224c6eb68ee4ae69
    3636
    37 platforms       darwin
     37platforms       darwin
    3838
    3939post-destroot {
    40         set docdir ${destroot}${prefix}/share/doc/${name}
     40    set docdir ${destroot}${prefix}/share/doc/${name}
    4141
    42         xinstall -d -m 755 ${docdir}
     42    xinstall -d -m 755 ${docdir}
    4343
    44         foreach f {CHANGES.txt CONTRIBUTORS.txt COPYING.txt INSTALL.txt README.txt examples} {
    45                 file copy ${worksrcpath}/${f} ${docdir}
    46         }
     44    foreach f {CHANGES.txt CONTRIBUTORS.txt COPYING.txt INSTALL.txt README.txt examples} {
     45        file copy ${worksrcpath}/${f} ${docdir}
     46    }
    4747}
    4848
    49 test.run        yes
    50 test.target     check
     49test.run        yes
     50test.target     check