Re: Sets, subsets, syspkgs, and MK*

To: Greg Troxel <gdt%ir.bbn.com@localhost>
Subject: Re: Sets, subsets, syspkgs, and MK*
From: Masao Uebayashi <uebayasi%tombi.co.jp@localhost>
Date: 2009年12月16日 01:36:20 +0900

> My understanding is that you need to know the build options for the
> previous build to provide patch files for binary updates.
> At least I think this is the reason why this thread was started.
> 
> I think this requires some kind of configuration storage in the binaries.
Definitely.
> Or it requires some CM discipline on the part of people who are changing
> options.
> 
> In the NetBSD repo, we have rules that we don't change certain things on
> stable branches, like shlib major version. Not changing the default
> settings of USE/MK is simply part of this. Anyone who's making private
> builds and wants to use binary patches is in the same boat with CM
> rules.
> 
> /etc/release already has the MK/USE state.
I keep forgetting /etc/release. We should simply convert it to an ordinally
/etc/netbsd_config.mk and use it while building. Because those variable
values are persistent during build.
Masao
-- 
Masao Uebayashi / Tombi Inc. / Tel: +81-90-9141-4635

References:
- Re: Sets, subsets, syspkgs, and MK*
  - From: Masao Uebayashi
- re: Sets, subsets, syspkgs, and MK*
  - From: matthew green
- Re: Sets, subsets, syspkgs, and MK*
  - From: Masao Uebayashi
- Re: Sets, subsets, syspkgs, and MK*
  - From: Greg Troxel
- Re: Sets, subsets, syspkgs, and MK*
  - From: Bernd Ernesti
- Re: Sets, subsets, syspkgs, and MK*
  - From: Greg Troxel

Prev by Date: Re: Sets, subsets, syspkgs, and MK*
Next by Date: Re: Sets, subsets, syspkgs, and MK*
Previous by Thread: Re: Sets, subsets, syspkgs, and MK*
Next by Thread: Re: Sets, subsets, syspkgs, and MK*
Indexes:

Home | Main Index | Thread Index | Old Index