Ticket #17537: Portfile.diff

Portfile

@@ -2 +2 @@
 
 PortSystem 1.0
 
-name            protobuf-cpp
-version         2.0.2
-categories      devel
-maintainers     blair
-description     Encode data in an efficient yet extensible format.
-
+name            protobuf-cpp
+version         2.0.3
+categories      devel
+maintainers     blair
+description     Encode data in an efficient yet extensible format.
+            
 long_description \
-                Google Protocol Buffers are a flexible, efficient, \
-                automated mechanism for serializing structured data -- \
-                think XML, but smaller, faster, and simpler.  You \
-                define how you want your data to be structured once, \
-                then you can use special generated source code to \
-                easily write and read your structured data to and from \
-                a variety of data streams and using a variety of \
-                languages.  You can even update your data structure \
-                without breaking deployed programs that are compiled \
-                against the "old" format.  You specify how you want \
-                the information you're serializing to be structured by \
-                defining protocol buffer message types in .proto \
-                files.  Each protocol buffer message is a small \
-                logical record of information, containing a series of \
-                name-value pairs.
-
-homepage        http://code.google.com/p/protobuf/
-master_sites    googlecode:protobuf
-
-distname        protobuf-${version}
-use_bzip2       yes
-checksums       md5 6674270b1d63c2c4b292644f48fede4e \
-                sha1 b3ebd8895000bb11ded88b1f207cb799653befa0 \
-                rmd160 bd76eeef45342a44b80a5bbf38ee28ccec021eea
+                Google Protocol Buffers are a flexible, efficient, \
+                automated mechanism for serializing structured data -- \
+                think XML, but smaller, faster, and simpler.  You \
+                define how you want your data to be structured once, \
+                then you can use special generated source code to \
+                easily write and read your structured data to and from \
+                a variety of data streams and using a variety of \
+                languages.  You can even update your data structure \
+                without breaking deployed programs that are compiled \
+                against the "old" format.  You specify how you want \
+                the information you're serializing to be structured by \
+                defining protocol buffer message types in .proto \
+                files.  Each protocol buffer message is a small \
+                logical record of information, containing a series of \
+                name-value pairs.
+
+homepage        http://code.google.com/p/protobuf/
+master_sites    googlecode:protobuf
+
+distname        protobuf-${version}
+use_bzip2       yes
+checksums       md5 37e6e4d63434672c70bd977be9c372cb \
+                sha1 aad5cbe1423060b0ff315d2a1447e7bf1209dc63 \
+                rmd160 624ea3075ba5756106c367be224c6eb68ee4ae69
 
-platforms       darwin
+platforms       darwin
 
 post-destroot {
-        set docdir ${destroot}${prefix}/share/doc/${name}
+    set docdir ${destroot}${prefix}/share/doc/${name}
 
-        xinstall -d -m 755 ${docdir}
+    xinstall -d -m 755 ${docdir}
 
-        foreach f {CHANGES.txt CONTRIBUTORS.txt COPYING.txt INSTALL.txt README.txt examples} {
-                file copy ${worksrcpath}/${f} ${docdir}
-        }
+    foreach f {CHANGES.txt CONTRIBUTORS.txt COPYING.txt INSTALL.txt README.txt examples} {
+        file copy ${worksrcpath}/${f} ${docdir}
+    }
 }
 
-test.run        yes
-test.target     check
+test.run        yes
+test.target     check