On Mon, Aug 07, 2006 at 05:03:57PM -0400, Kris Kennaway wrote:
> On Tue, Aug 08, 2006 at 12:24:49AM +0400, Boris Samorodov wrote:
> > On Mon, 7 Aug 2006 15:12:03 -0500 Brooks Davis wrote:
> > > On Mon, Aug 07, 2006 at 11:56:46PM +0400, Boris Samorodov wrote:
> > > > On Mon, 7 Aug 2006 14:37:25 -0400 Kris Kennaway wrote:
> > > > > On Mon, Aug 07, 2006 at 03:12:06AM +0400, Boris Samorodov wrote:
> > > > 
> > > > > > We have got a port (lang/gnat-gcc34) which has both bz2 and gz
> > > > > > distfiles. As for 5.x+ extracting is gone automagically. But not at
> > > > > > 4.x. Well, at 4.x extracting may be done for example, by using
> > > > > > USE_BZIP2 knob and doing gunzipping at after-extract:.
> > > > > > 
> > > > > > Does someone know a better solution?
> > > > > > Does we have examples at our ports?
> > > > 
> > > > > Use a do-extract that extracts all distfiles or EXTRACT_ONLY with
> > > > > post-extract that extracts the other ones.
> > > > 
> > > > Thanks, Kris. I'm trying to test (actually, to find an 4.x system)
> > > > some broken ports with a patch(es) which includes (thanks Brooks):
> > > > -----
> > > > .if ${OSVERSION} < 500000
> > > > EXTRACT_DEPENDS+=       bsdtar:${PORTSDIR}/archivers/libarchive
> > > > TAR=            /usr/local/bin/bsdtar
> > > > .endif
> > > > -----
> > > > 
> > > > To me that seems a good solution.
> > 
> > > I'd suggest using not using an absolute path in the TAR definition
> > > since the dependency check doesn't and using 502111 as the version since
> > > that's the first version bump after the initial bsdtar import.  Not that
> > > we really need to worry about such early 5.x release, but it's more
> > > correct.
> > 
> > Thanks again, Brooks. The patch will include (if Kris won't complain):
> > -----
> > .if ${OSVERSION} < 502111
> > EXTRACT_DEPENDS+=       bsdtar:${PORTSDIR}/archivers/libarchive
> > TAR=            bsdtar
> > .endif
> > -----
> 
> Actually I think you do need the absolute path, since it wont always
> be set in the environment (think crontabs, etc).  The correct
> specification would be ${LOCALBASE}/bin/bsdtar.

My thought was that the dependency check will fail if it's not in the
path so there's no point in having the absolute path in the TAR part.

-- Brooks

Attachment: pgpBasjbeN2yu.pgp
Description: PGP signature

Reply via email to