From owner-freebsd-ports  Mon Sep 27 13:40:37 1999
Delivered-To: freebsd-ports@freebsd.org
Received: from mango.attlabs.att.com (gate.ipo.att.com [135.197.57.2])
	by hub.freebsd.org (Postfix) with ESMTP id BC2E514D0E
	for <ports@freebsd.org>; Mon, 27 Sep 1999 13:40:35 -0700 (PDT)
	(envelope-from fenner@mango.attlabs.att.com)
Received: (from fenner@localhost)
	by mango.attlabs.att.com (8.9.3/8.9.3) id NAA69605
	for ports@freebsd.org; Mon, 27 Sep 1999 13:40:34 -0700 (PDT)
	(envelope-from fenner)
Date: Mon, 27 Sep 1999 13:40:34 -0700 (PDT)
From: Bill Fenner <fenner@research.att.com>
Message-Id: <199909272040.NAA69605@mango.attlabs.att.com>
To: ports@freebsd.org
Subject: Bad interaction between libtool version check and patches
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

  I was trying to install linux_base, which tried to install rpm, which
tried to install gdbm.  gdbm complained that my libtool was out of
date; so I pushd /usr/ports/whatever/libtool; make install; popd.
Now I'm back in linux_base, and I say "make" again, but this time
the gdbm port fails because its patches were already applied and it's
trying to patch again.

  It'd be nice if failing the libtool version check didn't leave the
port in an inconsistent state; now I have to go down 2 levels of
dependencies (or scroll back past 50 lines of "Exit 1") and make clean.
I don't have any brilliant suggestions, other than splitting the
patch-libtool target into pre-patch-libtool which checks the version
and post-patch-libtool which does whatever else.

  Bill


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