Hi pkg-team, with 151 I was (image-)updating packages from a non-Solaris repository with a command like: # pkg update -v --be-name <new_be>
but there was no new BE created and the packages were installed into the current BE. I later noticed new --require-new-be option to the update command. When I use the update with --be-name, isn't it enough to assume that I expect a new BE to be created, wdyt? This way the option is ignored. I'm not sure now if I didn't overlook that, but a warning about this would be nice. Regards, hnhn -- Jan Hnatek [email protected] _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
