Subject: Re: Proper use of .../NetBSD-current/tar_files/pkgsrc.tar.gz
To: David Brownlee <firstname.lastname@example.org>
From: Bill Squier <email@example.com>
Date: 04/17/1999 11:48:04
In message <Pine.GSO.firstname.lastname@example.org>, David Brownlee writes:
>On Fri, 16 Apr 1999, Bill Squier wrote:
>> > pkgsrc is designed to still be usable on the last release, so you
>> > _should_ be fine.
>> But this currently isn't true.
>> /pub/NetBSD-current/tar_files/pkgsrc.tar.gz will fail on a system
>> without an up-to-date /usr/share/mk/bsd.own.mk (one that understands
>> GNU_MACHINE_ARCH mappings). Anything that uses GNU autoconf will
> Then this is a error, and someone should submit a PR - please do
>> Or am I being bitten by a 1.3.2 / 1.3.3 difference here?
This is a 1.3.2 / 1.3.3 difference. Does anyone still consider it a bug?
(i.e., worthy of a send-pr) I only discovered it because I have a couple
of machines running 1.3.2 at home.
On 1.3.3, /usr/share/mk/bsd.own.mk is:
$NetBSD: bsd.own.mk,v 184.108.40.206 1998/11/07 01:12:25 cgd Exp $
and on 1.3.2, it's:
$NetBSD: bsd.own.mk,v 220.127.116.11 1998/02/07 00:32:36 mellon Exp $
The difference is that 18.104.22.168 has the GNU_MACHINE_ARCH mappings in it.
Until recently, pkgsrc had a makefile with these mappings.