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 22:02:59 +0900, Masao Uebayashi wrote:

> > i object pretty strenuously against any plans to remove most
> > of the MK* variables and some of the USE* in our tree.
> 
> I've never said to remove those variables...
> 
> Those variables will be sanitized by bsd.own.mk.  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 still haven't seen a coherent explanation of

1) what you are going to do
2) why that needs to be done

I'm sorry, but "I'm confused about MK* vs. USE*" doesn't sound like a
convincing enough reason.

SY, Uwe
-- 
uwe%stderr.spb.ru@localhost                       |       Zu Grunde kommen
http://snark.ptc.spbu.ru/~uwe/          |       Ist zu Grunde gehen


Home | Main Index | Thread Index | Old Index