Shawn Walker wrote:
[snip]
* a tool to dump a manifest from an import suitable for editing, etc.
I'm torn as to whether we could just add a '--dump' or the like
option to the 'import' subcommand of pkgsend or whether a separate
tool is more appropriate.
I had a "pkgsend -o" wad worked up some time ago, but was never
convinced I
had it designed right. I think the dump should be part of pkgsend, but
it's not clear to me whether it should be a flag to open, import,
close, or
some combination. Or even just another subcommand that does nothing but
dump a manifest representing a bundle, leaving you to
open/include/close an
actual transaction (and requiring that include be able to pull files not
just from a directory tree, but from the original tarfile).
I can't decide between a subcommand or a "-o" to import either.
I think this is a useful enough feature that not having it because we
can't decide whether it should be a subcommand or an option seems like
putting the cart before the horse to me.
My (weak) opinion is that it should be a subcommand because there are
options we'll likely want to add to change the format of the output. For
example, a flag to remove the hash information from files and replace
them with paths so that the output can be used with pkgsend include. Of
course, that could be another option that's only permissible with the -o
option.
There's a lot of things we can do to make publication easier, but this
is an important first step.
Brock
Cheers,
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
