<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ports/shells/bashc, branch release/8.0.0</title>
<subtitle>FreeBSD ports tree</subtitle>
<id>https://cgit-dev.freebsd.org/ports/atom?h=release%2F8.0.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/ports/atom?h=release%2F8.0.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/'/>
<updated>2008-08-21T06:18:49Z</updated>
<entry>
<title>Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.</title>
<updated>2008-08-21T06:18:49Z</updated>
<author>
<name>Rong-En Fan</name>
<email>rafan@FreeBSD.org</email>
</author>
<published>2008-08-21T06:18:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=741aa714833b9bb1e9afaaf5124d3f5c60b5e49c'/>
<id>urn:sha1:741aa714833b9bb1e9afaaf5124d3f5c60b5e49c</id>
<content type='text'>
Specifically, newer autoconf (&gt; 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 -&gt; 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)
</content>
</entry>
<entry>
<title>Bash Commander is a traditional GNU bash shell extended with visual two-panel</title>
<updated>2008-03-11T22:38:46Z</updated>
<author>
<name>Alejandro Pulver</name>
<email>alepulver@FreeBSD.org</email>
</author>
<published>2008-03-11T22:38:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=88863d272aad40c5e1cd8db2b414e1f48d067517'/>
<id>urn:sha1:88863d272aad40c5e1cd8db2b414e1f48d067517</id>
<content type='text'>
file browser.

Features:

* Full bash compatibility.
* Embedded visual file browser.
* Two file panels, turned on and off by pressing ^O.
* Actions and colors configured via .bashrc script.
* Run current file on pressing Enter, configurable via commander_start_file()
  shell function.
* Perform an action on pressing F1-F20 keys, configurable via commander_fN()
  shell functions.

WWW:	http://groups.google.com/group/bashc/web/overview
</content>
</entry>
</feed>
