Re: Proposed fix for long-standing +CONTENTS bug

[Greg Troxel <gdt%lexort.com@localhost>]

Jonathan Perkin <jperkin%joyent.com@localhost> writes:

> I mean where replace.mk goes and changes the +CONTENTS files and
> alters @pkgdep lines to now match installed packages instead of what
> the package was actually built with.  I get why it does that, but I
> really don't like the thought of an installed package being modified
> to be different from its binary package contents just to appease an
> inconsistent pkgdb.

I see.  I agree that this munging is bad.

It might be good to have the entire db plan and "database constraints"
written down in a design document kind of way.   This is seeming
complicated enough that I suspect only a few of you (you and David?)
100% understand.