ports/misc/patchutils, branch release/7.4.0FreeBSD ports treehttps://cgit-dev.freebsd.org/ports/atom?h=release%2F7.4.02010-02-23T18:07:14ZUpdate my mail address to @FreeBSD.org2010-02-23T18:07:14ZJohan van Selstjohans@FreeBSD.org2010-02-23T18:07:14Zurn:sha1:4aaac0b5f91fc973f5d39a99bd227267b1d5e5fa
Feature safe: yes
- Update to 0.3.12009-01-30T10:53:33ZJohan van Selstjohans@FreeBSD.org2009-01-30T10:53:33Zurn:sha1:74c6d14637e5288a9104b5ba441f60be3683f821
- Grab maintainership
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.2008-08-21T06:18:49ZRong-En Fanrafan@FreeBSD.org2008-08-21T06:18:49Zurn:sha1:741aa714833b9bb1e9afaaf5124d3f5c60b5e49c
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
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)
- Update to 0.3.02008-07-03T19:19:59ZPietro Ceruttigahr@FreeBSD.org2008-07-03T19:19:59Zurn:sha1:1b892ef142e6cd1ec64c3eb66fd59fd9e3ce50e5
PR: 125235
Submitted by: Ports Fury
- Remove USE_GETOPT_LONG which is a no-op since March 20072008-03-20T09:56:52ZPav Lucistnikpav@FreeBSD.org2008-03-20T09:56:52Zurn:sha1:9fc1c4fe89616480338adc0d98d5b1f0e4175302- Add SHA2562005-11-25T16:09:33ZPav Lucistnikpav@FreeBSD.org2005-11-25T16:09:33Zurn:sha1:70231c0b10d885a3183985ead912b3f479d8b5b6Update to 0.2.312005-06-15T16:41:16ZSergey Skvortsovskv@FreeBSD.org2005-06-15T16:41:16Zurn:sha1:bd5cefe191585e51462958a6f4b127a86fa53535At Kris's request, back out the MACHINE_ARCH spelling correction until2005-04-12T03:26:56ZDavid E. O'Brienobrien@FreeBSD.org2005-04-12T03:26:56Zurn:sha1:c3d8037aeba75366ed06e02fbc981e15b46e7d0a
after 5.4-RELEASE.
Assist getting more ports working on AMD64 by obeying the2005-04-11T08:04:41ZDavid E. O'Brienobrien@FreeBSD.org2005-04-11T08:04:41Zurn:sha1:f2fc2d60ae226a1b8d5411fb4aab91ea92be6f91
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.
upgrade to 0.2.302004-07-23T09:46:32ZYing-Chieh Liaoijliao@FreeBSD.org2004-07-23T09:46:32Zurn:sha1:c23f3a9054f3ec9168eb960df179665d12a6dd6f