I'd then need code in the svc-pkg-mirror method script to create datasets
_if_ the 'config/repositories' SMF property pointed at a directory that
happened to be at the top level of a container dataset in which we have
permissions to create child datasets.
.. which all seems pretty messy because it won't be obvious if we haven't
been able to create a separate dataset for the repository because of a
misconfiguration, or because the user intentionally doesn't want a separate
dataset for the repository.
Would it make sense to *always* create such a dataset in some other
(core) smf(5) service if it doesn't exist and then rely on the user to
enable the pkgrecv smf(5) service if they want it? It would mean by
default there would be an empty dataset sitting around even on systems
that aren't going to mirror but that seems like a small price to pay.
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
