Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Aug 2001 19:40:28 -0700 (PDT)
From:      "Matthew Emmerton" <matt@gsicomp.on.ca>
To:        freebsd-ports@FreeBSD.org
Subject:   Re: ports/29856: make extract of cyrus did an install of cyrus-sasl
Message-ID:  <200108190240.f7J2eST71256@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/29856; it has been noted by GNATS.

From: "Matthew Emmerton" <matt@gsicomp.on.ca>
To: <postmaster@shikahrsoho.com>, <FreeBSD-gnats-submit@FreeBSD.ORG>
Cc: <asami@FreeBSD.ORG>
Subject: Re: ports/29856: make extract of cyrus did an install of cyrus-sasl
Date: Sat, 18 Aug 2001 22:32:55 -0400

 This is apparently the desired behaviour, as all "build" and "lib"
 dependencies are built and installed during the extract phase of a port.
 
 However, the comment about the extract target in bsd.port.mk doesn't
 indicate this:
 
 # extract       - Unpacks ${DISTFILES} into ${WRKDIR}.
 
 I don't really see the need to 'make install' all build/lib/misc-depends
 during the extract phase.  In fact, the comment for the BUILD_DEPENDS
 indicates that these will be built 'between the "extract" and "build"
 stages', not *during* the extract phase.
 
 Could the making of build/lib/misc-depends be moved elsewhere?  Yes, I know
 that 'make extract NO_DEPENDS=YES' will suppress dependency building, but
 it's not what most people would think (or know) to do.  I would suggest
 pre-configure, since the 'patch' target shouldn't require anything other
 than 'patch', whereas the configure target would definitely require any
 dependent libraries or headers to be installed, especially if GNU configure
 is involved.
 
 --
 Matt Emmerton
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108190240.f7J2eST71256>