Number of commits found: 37

- update DEPRECATED line to point to the correct port

Approved by:    flz
Feature safe:   yes

- add EXPIRATION_DATE
Submitted by:   crees

- set CONFLICTS
PR:             163592

- set DEPRECATED
PR:             163592

- drop WWW

Sync to new bsd.autotools.mk

- Retire MASTER_SITE_SOURCEFORGE_EXTENDED, it's no longer needed - all mirrors
actually have all distfiles
- Merge all SF mirrors to MASTER_SITE_SOURCEFORGE, resort according to quick
download speed survey
- Fix MASTER_SITES for all port that have used SOURCEFORGE_EXTENTED

Approved by:    portmgr (pav)

-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22.
-Update libtool and libltdl to 2.2.6a.
-Remove devel/libtool15 and devel/libltdl15.
-Fix ports build with libtool22/libltdl22.
-Bump ports that depend on libltdl22 due to shared library version change.
-Explain what to do update in the UPDATING.

It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop
and applications in the runtime.

With help:      marcus and kwm
Pointyhat-exp:  a few times by pav
Tested by:      pgollucci, "Romain Tartière" <romain@blogreen.org>, and
                a few MarcusCom CVS users. Also, I might have missed a few.
Repocopy by:    marcus
Approved by:    portmgr

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 )

- new MASTER_SITE
Submitted by:   Wayne Zhou

- Replace USE_XLIB with USE_XORG=sm x11
- Bump PORTREVISION

PR:             ports/115077
Approved by:    dinoex (maintainer, private e-mail)

- list detailed dependencies
PR:             115077
Submitted by:   mm

- Welcome X.org 7.2 \o/.
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.

- make portlint happy

Use libtool port instead of included version to avoid objformat a.out botch

- take maintainership

Add a patch to prevent a segfault under certain circumstances.

Submitted by:   Mark Martinec via freebsd-ports
Obtained from:  http://fuzzyocr.own-hero.net/wiki/Downloads

- s,INSTALLS_SHLIB,USE_LDCONFIG,g
- these include dns/ editors/ emulators/ finance/
  games/ graphics/ maintained by ports@

PR:             ports/101916
Submitted by:   Gea-Suan Lin <gslin_AT_gslin dot org>

Conversion to a single libtool environment.

Approved by:    portmgr (kris)

Mass-conversion to the USE_AUTOTOOLS New World Order.  The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.

Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.

Preliminary documentation can be found at:
        http://people.FreeBSD.org/~ade/autotools.txt

which is in the process of being SGMLized before introduction into the
Porters Handbook.

Light blue touch-paper.  Run.

- Update to 4.1.4

PR:             ports/88346
Submitted by:   KATO Tsuguru <tkato432@yahoo.com>

At Kris's request, back out the MACHINE_ARCH spelling correction until
after 5.4-RELEASE.

Assist getting more ports working on AMD64 by obeying the
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.

Apply a big libtool patch to allow porters to use the libtool installed by
the libtoolX ports instead of the one included with each port.  Ports that
set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of
the included version.  To restore previous behavior, use the new macro,
USE_INC_LIBTOOL_VER.  Both macros accept the same argument: a libtool version.

For example, to use the ports version of libtool-1.5, add the following to
your Makefile:

USE_LIBTOOL_VER=        15

To use the included version of libtool with extra hacks provided by
libtool-1.5, add the following to your Makefile:

USE_INC_LIBTOOL_VER=    15

With this change, ports that had to add additional libtool hacks to prevent
.la files from being installed or to fix certain threading issues can now
delete those hacks (after appropriate testing, of course).

PR:             63944
Based on work by:eik and marcus
Approved by:    ade (autotools maintainer)
Tested by:      kris on pointyhat
Bound to be hidden problems:    You bet

- Update to 4.1.3

PR:             ports/67366
Submitted by:   Kimura Fuyuki <fuyuki@hadaly.org>

- Update to 4.1.2

PR:             ports/65156
Submitted by:   Kimura Fuyuki <fuyuki@hadaly.org>

Whoa there, boy, that's a mighty big commit y'all have there...

Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".

For ports-in-waiting:

        USE_LIBTOOL=YES         ->      USE_LIBTOOL_VER=13
        USE_AUTOCONF=YES        ->      USE_AUTOCONF_VER=213
        USE_AUTOMAKE=YES        ->      USE_AUTOMAKE_VER=14

Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.

For some mysterious reason, libungif prefers the antiquated <varargs.h>
to <stdarg.h>.  Unfortunately, it fails to build with gcc 3.3, so hack
configure to not test for the presence of <varargs.h>.

de-pkg-comment

Add another MASTER_SITE.

PR:             ports/42800
Submitted by:   Kimura Fuyuki <fuyuki@hadaly.org>

USE_LIBTOOL implies GNU_CONFIGURE, so remove the latter where appropriate.    

Standartise the way used to disable X11 support in various ports. From now   on
WITHOUT_X11 is the Only True Way[tm].    

Put the USE_LIBTOOL back where I put it.    

Make  it  possible  to  compile  this  package  without  X11  --   controllable
by the NO_X knob.    

Update to 4.1.0b1.    

Rename INSTALLS_SHLIBS to INSTALLS_SHLIB.  (There was a typo in the   previous
commit message to bsd.port.mk, which said INSTALL_SHLIBS.  Boo.)    

Fourth round of INSTALLS_SHLIBS conversion.    

Number of commits found: 37

12 vulnerabilities affecting 17 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities