[53308] trunk/dports/devel
blair at macports.org
blair at macports.org
Thu Jul 2 17:32:43 PDT 2009
Revision: 53308
http://trac.macports.org/changeset/53308
Author: blair at macports.org
Date: 2009-07-02 17:32:43 -0700 (Thu, 02 Jul 2009)
Log Message:
-----------
Untabify.
Modified Paths:
--------------
trunk/dports/devel/protobuf-cpp/Portfile
trunk/dports/devel/protobuf-java/Portfile
trunk/dports/devel/protobuf-python/Portfile
trunk/dports/devel/protobuf-python25/Portfile
trunk/dports/devel/protobuf-python26/Portfile
Modified: trunk/dports/devel/protobuf-cpp/Portfile
===================================================================
--- trunk/dports/devel/protobuf-cpp/Portfile 2009-07-03 00:30:01 UTC (rev 53307)
+++ trunk/dports/devel/protobuf-cpp/Portfile 2009-07-03 00:32:43 UTC (rev 53308)
@@ -2,53 +2,53 @@
PortSystem 1.0
-name protobuf-cpp
-version 2.1.0
-categories devel
-maintainers blair
-description Encode data in an efficient yet extensible format.
+name protobuf-cpp
+version 2.1.0
+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.
+ 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
+homepage http://code.google.com/p/protobuf/
+master_sites googlecode:protobuf
-distname protobuf-${version}
-use_bzip2 yes
-checksums md5 7aedd257d8723c128cc1529c4675f858 \
- sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
- rmd160 f209732febc8d4cc321246c5caff2b7502d13073
+distname protobuf-${version}
+use_bzip2 yes
+checksums md5 7aedd257d8723c128cc1529c4675f858 \
+ sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
+ rmd160 f209732febc8d4cc321246c5caff2b7502d13073
-platforms darwin
+platforms darwin
-configure.cflags-append -g
-configure.cppflags-append -g
+configure.cflags-append -g
+configure.cppflags-append -g
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.cmd "ulimit -c 0; make"
-test.target check
+test.run yes
+test.cmd "ulimit -c 0; make"
+test.target check
Modified: trunk/dports/devel/protobuf-java/Portfile
===================================================================
--- trunk/dports/devel/protobuf-java/Portfile 2009-07-03 00:30:01 UTC (rev 53307)
+++ trunk/dports/devel/protobuf-java/Portfile 2009-07-03 00:32:43 UTC (rev 53308)
@@ -1,63 +1,63 @@
# $Id$
-PortSystem 1.0
+PortSystem 1.0
-name protobuf-java
-version 2.1.0
-categories devel
-maintainers blair
-description Encode data in an efficient yet extensible format.
+name protobuf-java
+version 2.1.0
+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.
+ 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
+homepage http://code.google.com/p/protobuf/
+master_sites googlecode:protobuf
-distname protobuf-${version}
-dist_subdir protobuf-cpp
-use_bzip2 yes
-checksums md5 7aedd257d8723c128cc1529c4675f858 \
- sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
- rmd160 f209732febc8d4cc321246c5caff2b7502d13073
+distname protobuf-${version}
+dist_subdir protobuf-cpp
+use_bzip2 yes
+checksums md5 7aedd257d8723c128cc1529c4675f858 \
+ sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
+ rmd160 f209732febc8d4cc321246c5caff2b7502d13073
-platforms darwin
+platforms darwin
-depends_lib port:protobuf-cpp
-depends_build port:apache-ant
+depends_lib port:protobuf-cpp
+depends_build port:apache-ant
-worksrcdir ${worksrcdir}/java
+worksrcdir ${worksrcdir}/java
patch {
- file copy ${filespath}/build.xml ${worksrcpath}/
+ file copy ${filespath}/build.xml ${worksrcpath}/
}
-use_configure no
+use_configure no
-build.cmd ant
-build.target jar api
+build.cmd ant
+build.target jar api
destroot {
- set javadir ${destroot}${prefix}/share/java
- set docdir ${destroot}${prefix}/share/doc/${name}
+ set javadir ${destroot}${prefix}/share/java
+ set docdir ${destroot}${prefix}/share/doc/${name}
- xinstall -d -m 755 ${javadir}
- xinstall -d -m 755 ${docdir}
+ xinstall -d -m 755 ${javadir}
+ xinstall -d -m 755 ${docdir}
- file copy ${worksrcpath}/protobuf.jar ${javadir}
- file copy ${worksrcpath}/api ${docdir}/api
+ file copy ${worksrcpath}/protobuf.jar ${javadir}
+ file copy ${worksrcpath}/api ${docdir}/api
}
Modified: trunk/dports/devel/protobuf-python/Portfile
===================================================================
--- trunk/dports/devel/protobuf-python/Portfile 2009-07-03 00:30:01 UTC (rev 53307)
+++ trunk/dports/devel/protobuf-python/Portfile 2009-07-03 00:32:43 UTC (rev 53308)
@@ -1,48 +1,48 @@
# $Id$
-PortSystem 1.0
-PortGroup python24 1.0
+PortSystem 1.0
+PortGroup python24 1.0
-name protobuf-python
-version 2.1.0
-categories devel
-maintainers blair
-description Encode data in an efficient yet extensible format.
+name protobuf-python
+version 2.1.0
+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.
+ 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
+homepage http://code.google.com/p/protobuf/
+master_sites googlecode:protobuf
-distname protobuf-${version}
-dist_subdir protobuf-cpp
-use_bzip2 yes
-checksums md5 7aedd257d8723c128cc1529c4675f858 \
- sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
- rmd160 f209732febc8d4cc321246c5caff2b7502d13073
+distname protobuf-${version}
+dist_subdir protobuf-cpp
+use_bzip2 yes
+checksums md5 7aedd257d8723c128cc1529c4675f858 \
+ sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
+ rmd160 f209732febc8d4cc321246c5caff2b7502d13073
-platforms darwin
+platforms darwin
-depends_lib port:protobuf-cpp \
- port:py-setuptools
+depends_lib port:protobuf-cpp \
+ port:py-setuptools
-worksrcdir ${worksrcdir}/python
+worksrcdir ${worksrcdir}/python
-test.run yes
-test.cmd "${prefix}/bin/python2.4 setup.py"
-test.target test
+test.run yes
+test.cmd "${prefix}/bin/python2.4 setup.py"
+test.target test
Modified: trunk/dports/devel/protobuf-python25/Portfile
===================================================================
--- trunk/dports/devel/protobuf-python25/Portfile 2009-07-03 00:30:01 UTC (rev 53307)
+++ trunk/dports/devel/protobuf-python25/Portfile 2009-07-03 00:32:43 UTC (rev 53308)
@@ -1,48 +1,48 @@
# $Id$
-PortSystem 1.0
-PortGroup python25 1.0
+PortSystem 1.0
+PortGroup python25 1.0
-name protobuf-python25
-version 2.1.0
-categories devel
-maintainers blair
-description Encode data in an efficient yet extensible format.
+name protobuf-python25
+version 2.1.0
+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.
+ 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
+homepage http://code.google.com/p/protobuf/
+master_sites googlecode:protobuf
-distname protobuf-${version}
-dist_subdir protobuf-cpp
-use_bzip2 yes
-checksums md5 7aedd257d8723c128cc1529c4675f858 \
- sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
- rmd160 f209732febc8d4cc321246c5caff2b7502d13073
+distname protobuf-${version}
+dist_subdir protobuf-cpp
+use_bzip2 yes
+checksums md5 7aedd257d8723c128cc1529c4675f858 \
+ sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
+ rmd160 f209732febc8d4cc321246c5caff2b7502d13073
-platforms darwin
+platforms darwin
-depends_lib port:protobuf-cpp \
- port:py25-setuptools
+depends_lib port:protobuf-cpp \
+ port:py25-setuptools
-worksrcdir ${worksrcdir}/python
+worksrcdir ${worksrcdir}/python
-test.run yes
-test.cmd "${prefix}/bin/python2.5 setup.py"
-test.target test
+test.run yes
+test.cmd "${prefix}/bin/python2.5 setup.py"
+test.target test
Modified: trunk/dports/devel/protobuf-python26/Portfile
===================================================================
--- trunk/dports/devel/protobuf-python26/Portfile 2009-07-03 00:30:01 UTC (rev 53307)
+++ trunk/dports/devel/protobuf-python26/Portfile 2009-07-03 00:32:43 UTC (rev 53308)
@@ -1,48 +1,48 @@
# $Id$
-PortSystem 1.0
-PortGroup python26 1.0
+PortSystem 1.0
+PortGroup python26 1.0
-name protobuf-python26
-version 2.1.0
-categories devel
-maintainers blair
-description Encode data in an efficient yet extensible format.
+name protobuf-python26
+version 2.1.0
+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.
+ 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
+homepage http://code.google.com/p/protobuf/
+master_sites googlecode:protobuf
-distname protobuf-${version}
-dist_subdir protobuf-cpp
-use_bzip2 yes
-checksums md5 7aedd257d8723c128cc1529c4675f858 \
- sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
- rmd160 f209732febc8d4cc321246c5caff2b7502d13073
+distname protobuf-${version}
+dist_subdir protobuf-cpp
+use_bzip2 yes
+checksums md5 7aedd257d8723c128cc1529c4675f858 \
+ sha1 042025cac0b8f76468091bc796d3fd8807a4664f \
+ rmd160 f209732febc8d4cc321246c5caff2b7502d13073
-platforms darwin
+platforms darwin
-depends_lib port:protobuf-cpp \
- port:py26-setuptools
+depends_lib port:protobuf-cpp \
+ port:py26-setuptools
-worksrcdir ${worksrcdir}/python
+worksrcdir ${worksrcdir}/python
-test.run yes
-test.cmd "${prefix}/bin/python2.6 setup.py"
-test.target test
+test.run yes
+test.cmd "${prefix}/bin/python2.6 setup.py"
+test.target test
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20090702/810282c6/attachment-0001.html>
More information about the macports-changes
mailing list