>>>>> Hubert Feyrer writes:

Hubert> Doing things the way they are, pkg_create just needs to know
Hubert> about one file format (PLIST), without adding hooks for the
Hubert> +CONTENTS file as well.

But aren't the two files in the same format?!

Hubert> Unformtunately, this will end up in a major rewrite of pkg_*
Hubert> which I doubt anyone will touch.

Hmm, are you really sure about this? I did a simple experiment: I
instrumented the bsd.pkg.mk file a bit, and the only real thing that
happen when I type "make package" in shells/bash2/ is:

/usr/sbin/pkg_create -v -c /usr/src/pkg/shells/bash2/pkg/COMMENT
	-d /usr/src/pkg/shells/bash2/pkg/DESCR
	-f /usr/src/pkg/shells/bash2/work/.PLIST
	-p /usr/pkg -P "" gtexinfo-3.12 -m /etc/mtree/BSD.pkg.dist
	/usr/src/pkg/shells/bash2/../../packages/All/bash-2.02.tgz

If I instead give /var/db/pkg/bash-2.02/+CONTENTS to the "-f" flag and
run the command manually, *exactly* the same binary package is built,
with one minor exception. In the latter case, the resulting +CONTENTS
contains duplicated "@comment MD5..." lines. But that seems easy to fix...

Hubert> (The pkg-upgrading-issue would need to be dealt with there, too...)

Yes, I realise that there might be some cases where my method will
break, but I'd like to understand why. For me it would make life much
easier if +CONTENTS could be used to build packages instead.

	-- Urban

P.S. Just in case it hasn't been clear. I think you guys are doing a
wonderful job with the package system! This problem is just a minor
detail. ;-)

--
FSF Panama spy arrangements explosion Treasury Ortega jihad Soviet
Legion of Doom assassination kibo plutonium Noriega bomb