Subject: Re: release granularity (Re: CVS commit: src)
To: Chuck Silvers <chuq@chuq.com>
From: Luke Mewburn <lukem@NetBSD.org>
List: port-i386
Date: 05/14/2004 09:50:07
--Ul2mxMk0z4RYCW0d
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, May 13, 2004 at 09:15:45AM -0700, Chuck Silvers wrote:
  | hi guys,
  |=20
  | I've suggested the following idea to a few people before,
  | and this thread seems like a good excuse to mention it again:
  |=20
  | it seems to me that it would make more sense to do builds based on
  | $(MACHINE_ARCH) than on $(MACHINE), since the vast majority of the
  | files in a release are the same for (eg.) all 11 or 12 of the m68k
  | platforms.  the few programs that are really only relevant on one
  | particular $(MACHINE) (such as grfconfig, which is only useful on amiga)
  | could be built and installed on other systems anyway.   someday when
  | we move to the syspkg stuff then the installation process can allow
  | people to skip installing such files on systems where they aren't usefu=
l.

this is a good idea in general, although we have some outstanding
toolchain issues to resolve as well.  i discovered some of these
whilst manually validating the contents of the "MACHINE_ARCH
sharable" sets for NetBSD 1.6 - certain binaries that should have
been bit-copies were not.  (PRs 18316 & 18317 are some examples)

i suggest we move this discussion as a separate thread to
tech-toolchain.

cheers,
luke.

--Ul2mxMk0z4RYCW0d
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFApAmvpBhtmn8zJHIRAgD6AJ92KUwT0zwmVGcLQBMbqOCcot4KWACeJ2jx
VoAD8MvagQ7FZXvrXmZ+4no=
=1S5Q
-----END PGP SIGNATURE-----

--Ul2mxMk0z4RYCW0d--