From owner-freebsd-ports Wed Oct 7 10:02:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28880 for freebsd-ports-outgoing; Wed, 7 Oct 1998 10:02:53 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28871 for ; Wed, 7 Oct 1998 10:02:47 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) for ports@freebsd.org id 0zQwyU-0002X8-00; Wed, 7 Oct 1998 12:02:06 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: What's the right way to handle old bsd.port.mk? To: ports@FreeBSD.ORG Date: Wed, 07 Oct 1998 12:02:06 -0500 Message-Id: Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hi, What should a port that needs to know PORTOBJFORMAT do on a system with an older bsd.port.mk? .include .if !defined(PORTOBJFORMAT) # bsd.port.mk must be out of date .error You need bsd.port.mk revision 1.227.2.51 or later for \ -STABLE, 1.287 or later for -CURRENT in order to build \ this port. .endif or assume PORTOBJFORMAT=aout? If the latter, how should one handle packaging? Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNhuejjeRhT8JRySpAQGIsgQAwQ+VG6KJYhHUryp+isE6J57FP4Vxxnht C721dIuKG6zf6E0ftmzfIZZKFH0fVkHwbrPoaeP/piJRNUjZFS6/cZRdOSHvagqR p8OukLp/056Njufrig5bQKVi4vgzsRM8nIDhJNYXRj6yLiTDpGuZH4iZkPYIMxfb IUNNHuGMxQw= =RSDJ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message