svn commit: r338172 - Now deprecating DRM

[Rodney W. Grimes]

[ Charset UTF-8 unsupported, converting... ]
> On Wed, Aug 22, 2018 at 10:08 AM Rodney W. Grimes <
> freebsd at pdx.rh.cn85.dnsmgr.net> wrote:
> 
> > I think this deprecation is a rather serious deviation
> > from the stated policy, in that 0 notification was
> > made, core IMHO, has overstepped some boundaries in
> > that respect.   These policies are promises to the
> > downstream consumers, and violating them is very
> > poor planning.
> >
> 
> Despite what the commit said, core didn't actually formally approve it
> before the fact. That was one of the many miscommunications surrounding
> this episode.

Well I would say inlight of that fact a revert should be a no questions
asked, doing much else risks build breakage within hours of code freeze.


> I don't think you'll find anybody who would say this was well planned or
> well executed.

Agreed, so lets be simple in correcting it?

>From some investigation even the claim that "in base drm conflicts with
ports drm" is not totally true, you just have to take a few steps to
be sure you do not load the base versions, and do load the ports version.

There is still time to revert this, add the gone_in(13) glue and have
12.0 go out in that state.

I am concerned that if 1 person came forward right off the bat with
this change, and we try to do something that takes care of just that
issue we are going to have others come forward in time with similiar
issues and we are going to look bad for failing to follow our own
published guidelines.

I see no smoking gun reason that this code has to die today,
the ports are already setup with instructions on how to deal
with the inbase drm.

-- 
Rod Grimes                                                 rgrimes at freebsd.org