tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Sets, subsets, syspkgs, and MK*

On Tue, Dec 15, 2009 at 10:04:04AM -0500, Greg Troxel wrote:
>   Those variables will be sanitized by  Same are renamed and
>   others are checked (integrity, consistency, conflicttion, dependency,
>   ...).
>   For example MKSOFTFLOAT will be converted to USE_SOFTFLOAT or
>   __USE_SOFTFLOAT or NETBSD_CONFIG_USE_SOFTFLOAT or whatever namespace
>   and used in the tree.  MKSOFTFLOAT stands as user interface.
> I would be happy to see any bugs in MK* and USE* fixed.  But I do not
> understand what the problem is and why mass renaming is helpful.  The
> MK* and USE* notion seems entirely sensible, and the only thing that is
> perhaps wrong is that the docs aren't good enough.

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.


Home | Main Index | Thread Index | Old Index