>> I think I really fouled something up in my workspace state for those
>> builds, and the only thing I can think of is that I had an interrupted
>> build in a workspace that I cloned using tar.
>
> Yikes ... ok.

Yeah, exactly contrary to your "don't pollute the main workspace" 
philosophy below.

>> I think what I'm willing to promise (jbeck and dmarker) is to not pollute
>> their findunref output with our putback. As long as we don't care about
>> successive sparc and i386 clobber builds for findunref in the same
>> workspace (who would DO such an icky thing?) we're pretty much there.
>
> I certainly don't do that.  I use separate child workspaces to do my
> per-architecture builds, so I don't pollute my main workspace with
> generated trash, and so that if something goes wrong, a quick rm -rf
> (or perhaps zfs destroy) gets me back to normal.
>
> But there do seem to be people who (for whatever reason) like to do
> alternating builds in a single workspace, and even a few who are
> disappointed that they can't do both x86 and SPARC in the same
> workspace at the same time.  I view them as mildly off-kilter (akin to
> desparately wanting to plumb "foo" as an IP interface name rather than
> "foo0," just because DLPI Style 1 appears to allow it), and I don't
> sweat it much.  Any time someone runs into a problem like that, I can
> always say, "no, that never happens to me."  ;-}

As Rich and I discussed in IRC, building sequentially in the same 
workspace is one thing.  Expecting findunref to produce clean results in 
such a scenario is another (much less reasonable) thing.

>>>     % ws /path/to/ws
>>>     % cd $SRC/tools
>>>     % dmake install
>>>
>>> Right?
>>
>> Nope.  It will just not include the scm-specific exception list entries.
>> But the tools that are built will be the same.
>
> Oh, right.  I was expecting that to expand badly, but it doesn't.  OK,
> then.

That failure mode comes if which_scm can't recognize the scm.  But I think 
it's safe to assume that you're doing your builds in a workspace managed 
by the scm that you use to manage your workspace.

>> Will push soon.
>
> Sounds good.

Thanks tons to you and Bill for being around so late on a Friday evening.

(Others, too, but I felt like I was being a bit demanding of you two in 
particular today.)

--Mark

Reply via email to