/games/outerspace/

lt='cgit logo'/> index : freebsd-ports-gnome
FreeBSD GNOME current development ports (https://github.com/freebsd/freebsd-ports-gnome)
aboutsummaryrefslogtreecommitdiffstats
path: root/news/nget
Commit message (Collapse)AuthorAgeFilesLines
* USE_GCC=any was a lie, nail down to GCC 4.8 as the latest versionGerald Pfeifer2015-01-202-2/+2
| | | | | | | | that will build this on FreeBSD 10 and later (without GCC). [1] On the way remove an instance of @dirrm from pkg-plist. PR: 196913 [1], 196712 [1]
* Add DOCS option for ports with PORTDOCS in plist.Adam Weinberger2014-07-161-0/+2
|
* Add the missing plist bitsBaptiste Daroussin2013-12-271-0/+2
|
* Support gccBaptiste Daroussin2013-12-271-16/+8
| | | | Fix build on head but enforcing gcc
* Add NO_STAGE all over the place in preparation for the staging support (cat: ↵Baptiste Daroussin2013-09-211-5/+2
| | | | news)
* - Get Rid MD5 supportMartin Wilke2011-03-201-1/+0
|
* Autotools update. Read ports/UPDATING 20100915 for details.Ade Lovett2010-09-161-1/+1
| | | | | Approved by: portmgr (for Mk/bsd.port.mk part) Tested by: Multiple -exp runs
* Add patch forgotten in previous commit. No functional change:Johan van Selst2010-05-141-0/+416
| | | | copy patch from aclocal.m4 to configure, so there's no need to run autoconf
* Remove unnecessary dependency on autoconfJohan van Selst2010-05-131-1/+1
|
* - Switch SourceForge ports to the new File Release System: categories ↵Dmitry Marakasov2009-08-221-2/+1
| | | | starting with N
* Fix with autoconf-2.62. After running autotools at the top level, theAde Lovett2008-08-271-0/+12
| | | | | | | code then goes on to run autoconf/autoheader *again* via its own mechanisms, with predictable results. Quite how this port *ever* built is beyond me, but hey, this fixes it.
* Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.Rong-En Fan2008-08-211-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* Catch up with a port that wasn't using autoconf:261 on my tree.Ade Lovett2008-08-201-1/+1
|