| There is a PORTS FREEZE in effect! |
|
A ports freeze
means that commits will be few and far between and only by approval.
|
| non port: devel/google-perftools/Makefile |
|
CVSWeb
|
Number of commits found: 7 |
|
Wed, 24 Sep 2008
|
[ 10:23 miwi ] 
1.7 devel/google-perftools/Makefile
1.4 devel/google-perftools/distinfo
- Update to 0.98
PR: 127333
Submitted by: Yuri <yuri@tsoft.com> (maintainer)
|
|
Thu, 21 Aug 2008
|
[ 07:18 rafan ]
1.4 accessibility/yasr/Makefile
1.15 archivers/advancecomp/Makefile
1.24 archivers/arj/Makefile
1.27 archivers/dact/Makefile
1.22 archivers/gzip/Makefile
1.10 archivers/libmspack/Makefile
1.3 archivers/libpar2/Makefile
1.37 archivers/lzo/Makefile
1.44 archivers/lzo2/Makefile
1.16 archivers/lzop/Makefile
(Only the first 10 of 1030 ports in this commit are shown above.  )
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk (Only the first 15 lines of the commit message are shown above )
|
|
Sun, 27 Apr 2008
|
[ 06:22 rafan ]
1.5 devel/google-perftools/Makefile
1.3 devel/google-perftools/distinfo
1.2 devel/google-perftools/pkg-plist
- Update to 0.9.7
PR: ports/123061
Submitted by: Yuri <yuri at tsoft.com> (maintainer)
|
|
Thu, 6 Mar 2008
|
[ 22:19 edwin ]
1.7 archivers/xar/Makefile
1.8 databases/memcachedb/Makefile
1.3 deskutils/gcalcli/Makefile
1.3 deskutils/nagaina/Makefile
1.4 devel/google-perftools/Makefile
1.15 devel/google-sparsehash/Makefile
1.14 devel/guichan/Makefile
1.4 devel/py-boto/Makefile
1.5 devel/py-parsedatetime/Makefile
1.10 devel/py-pefile/Makefile
(Only the first 10 of 39 ports in this commit are shown above. )
Use ${MASTER_SITE_GOOGLE_CODE} instead of
http://something.googlecode.com/files
PR: ports/121435 (related)
|
|
Wed, 12 Dec 2007
|
[ 11:43 vd ]
1.3 devel/google-perftools/Makefile
1.2 devel/google-perftools/distinfo
1.2 devel/google-perftools/pkg-descr
Upgrade devel/google-perftools from 0.93 to 0.94.
ChangeLog:
http://google-perftools.googlecode.com/svn/tags/perftools-0.94/ChangeLog
Submitted by: Yuri <yuri@rawbw.com> (maintainer)
|
|
Sun, 18 Nov 2007
|
[ 08:52 linimon ]
1.2 devel/google-perftools/Makefile
Broken on sparc64 as well as amd64.
While here, fix a typo.
Approved by: portmgr (self)
|
|
Thu, 11 Oct 2007
|
[ 16:36 vd ]
1.2906 devel/Makefile
1.1 devel/google-perftools/Makefile
1.1 devel/google-perftools/distinfo
1.1 devel/google-perftools/pkg-descr
1.1 devel/google-perftools/pkg-plist
Add new port devel/google-perftools:
Perf Tools is a collection of a high-performance multi-threaded malloc()
implementation, plus some pretty nifty performance analysis tools.
Perf Tools is the fastest memory allocation library available,
it also often allows applications to have smaller memory
footprint.
WWW: http://code.google.com/p/google-perftools
PR: ports/113689
Submitted by: Yuri <yuri@tsoft.com>
|
Number of commits found: 7 |
