apache port broken for 4.10 RELEASE?

[freebsd-stable at auscert.org.au]

Thanks Kent (and Phil and Udo).

I have a couple of questions though.

If 2.0.49 apache is broken in 4.10 release (install +ports), why do the
MD5 sums exist in distinfo for this particular version at all (rather than
just a simple "not supported for this release" error)

and

What benefit is there (apart from FreeBSD-friendly install paths) to
installing the port over than building from the standard sources anyway,
which I usually do and have done already with this combination or 4.10 and
2.0.49? And, I guess, why does it build successfully this way anyway?

cheers all,
-- Joel Hatton --
Security Analyst and FIRST Representative  | Hotline: +61 7 3365 4417
AusCERT - Australia's national CERT        | Fax:     +61 7 3365 7031
The University of Queensland               | WWW:     www.auscert.org.au
Qld 4072 Australia                         | Email:   auscert at auscert.org.au

> On Monday 05 July 2004 07:04 pm, freebsd-stable at auscert.org.au wrote:
> > Hi,
> >
> > When attempting to make in /usr/ports/www/apache2 I get the error:
> >
> > ===> apache-2.0.49 is marked as broken: unknown LIBTOOL version: 13
> >
> > Is there a solution for this?
> >
> 
> It wants something different. The current version of Apache is 2.0.50 
> and its dependancies are
> 
> Port:   apache-2.0.50
> Path:   /usr/ports/www/apache2
> Info:   Version 2 of Apache web server with prefork MPM.
> Maint:  clement at FreeBSD.org
> Index:  www ipv6
> B-deps: autoconf-2.59_1 expat-1.95.7 libiconv-1.9.1_3 libtool-1.5.6_1 
> m4-1.4_1 openssl-0.9.7d perl-5.8.4
> R-deps: expat-1.95.7 libiconv-1.9.1_3 openssl-0.9.7d perl-5.8.4 
> rc_subr-1.29
> 
> That built on 2 of my systems without any problems.
> 
> Kent
> 
> -- 
> Kent Stewart
> Richland, WA
> 
> http://users.owt.com/kstewart/index.html