Joerg Sonnenberger wrote:
> now that packages by default don't contain mtree specs, I would like to
> start disabling the mtree code in pkg_add as well and make it print a
> warning. Reasoning is that most cases never cared about it and it means
> that pkg_add is one step closer to being standalone.

I don't think *any* package actually used a custom mtree file.  Since 
tar took care of creating any directories for us anyway, I agree that we 
don't really need to run it for any binary packages that we have 
created, even those created a long, long time ago.

> The change does two things:
> (a) Always print a warning when the package contains a mtree specification.

This is good... we should at least note when we have something we 
weren't expecting anymore.

> (b) Always keep the mtree spec around (currently removed after use).

Where would we keep this file around after the binary package is unpacked?

	Cheers,

	-- Johnny Lam <jlam@buildlink.org>