Fallout from the CVS discussion

[Eitan Adler]

On 17 September 2012 17:52, Warner Losh <imp at bsdimp.com> wrote:
[snip]

>>>> There is a compromise solution here that I have been hesitant to offer
>>>> because I was really hoping that sanity would prevail. But why not
>>>> switch the default MK_CVS knob over to "no" now? That will give us an
>>>> opportunity to see if there really will be any fallout, and easily fix
>>>> it if there is.
>>>
>>> I believe that's already been done.
>>
>> It isn't now, but it sounds to me like you're saying that you're not
>> opposed to doing so?
>
> MK_CVS moving to 'no' by default is something we can do right away, since it is easy to figure out what went wrong for the people using cvs and putting it back w/o needing to download anything new.  Living behind firewalls can make downloads a pita.  I have had systems with very specific holes that made it a PITA to download anything to them, and it is a common occurrence.
>
>> Eitan, if you're listening, I'd strike while the iron is hot. :)
>
> Since I thought that had already been done, please do so.  Please make sure that ObsoleteFiles does the right thing too :)  Oh, and make sure UPDATING is updated.

I have some surrounding commits to get done first. I'd like to get
some of the existing documentation that refers to CVS removed or
modified first.
There is some consensus for making MK_CVS default to "no" early, so
I'll take that into account and commit that sooner than the above
listed conditions.
Does this change require a OSVERSION bump?  I'm inclined to say yes as
the ports infrastructure might need to be aware of the change.


-- 
Eitan Adler