I pulled over the latest source and tried using it on my depot, and am
getting these messages:
//lib/svc/method/svc-pkg-depot[183]: --cfg
svc:/application/pkg/server/dev:default: not found [No such file or
directory]
[ Jul 15 21:18:58 Stopping because all processes in service exited. ]
I'm obviously setting something incorrectly, but in looking at the
pkg-server.xml file that was delivered with this change, I can't see
what I am doing wrong with my "pkg-server-dev.xml" file.
svc-pkg-depot shows:
cmd="$wrapper ${pkg_root}usr/lib/pkg.depotd $bool_ops
$option_ops " \
"--cfg $SMF_FMRI"
But if the --cfg option can be a file, how does this get set?
It isn't picking up my manifest file's define of cfg_file.
-- Alan
On 07/ 8/10 11:53 AM, Shawn Walker wrote:
Greetings,
With the putback of changeset 1968 to the pkg(5) gate, pkg.depotd(1M)
now fully supports SMF and file-based configuration, and a new utility
has been added for creating and managing package repositories.
What changed?
=============
pkg.depotd(1M) now natively supports configuration of the depot server
using SMF, command line options, or a configuration file using the new
--cfg option.
Previously, SMF configuration could only be used when running
pkg.depotd using the service script and only some configuration could
be performed using a file. The depot server can now be fully
configured using SMF or a depot configuration file.
In addition, the properties that controlled the presentation and
generation of the RSS/Atom feed provided by the depot server are now
configured using SMF or a depot configuration file instead of through
the repository's cfg_cache file. See the new 'pkg_bui' property group
documented in pkg.depotd(1M).
Finally, pkgrepo(1) has been added as a utility for creating and
managing package repositories suitable for use with pkg.depotd(1M) or
standalone. pkgsend(1) should no longer be used to create
repositories. See the related man pages for details.
What does this mean?
====================
This change means that if the presentation of the depot server's feed
was previously customised using the repository's cfg_cache file, it
must now be done using SMF or a depot configuration file.
What are the related bug entries?
=================================
The following RFEs/Bugs were resolved by changeset 1968:
8722 advanced repository metadata store needed
15528 repository administration and configuration tool
16264 client operations fail if non-existent file repository is
configured
16397 repository.__set_file_root references unbound EACCESS
16404 coverage reports miss class initialization and module setup
16474 depot feed isn't always cached
What are the potential issues?
==============================
Other than the possible loss of existing RSS/Atom feed customisation
noted above, there are no expected migration issues.
Thanks
======
Many thanks to the individuals who collaborated on, reviewed, or
contributed to this project.
Cheers,
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
