tech-toolchain archive

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

Re: final steps for reproduceable builds.



On Mar 10,  5:32pm, perry%piermont.com@localhost ("Perry E. Metzger") wrote:
-- Subject: Re: final steps for reproduceable builds.

| 
| christos%zoulas.com@localhost (Christos Zoulas) writes:
| > | Fine, but we need something for each component too, and we need a name
| > | for that specifically here -- something that reflects that what we're
| > | dealing with is very specifically the "D" flag to ar on bsd.lib.mk
| > | built libraries.
| > | 
| > | Any ideas on a name for *that*? I've been unable to think of a good one.
| >
| > MKARZERO? But I don't know about making too many tunables available to the
| > user, they make things hard to test and maintain.
| 
| In this case I want to make it possible for non-NetBSD code to use
| bsd.lib.mk and turn on and off the D flag, which means it needs to be
| independently tunable.
| 
| If you prefer MKARZERO, I'll use that.

I just think something set to yes or no and it is a make tunable
should start with MK. This is the first thing came to mind. I still
think that providing this fine-grained user-visible tunables is just
a nightmare.

christos


Home | Main Index | Thread Index | Old Index