Skip to main content
Last updated March 07, 2013 17:25, by Shawn Walker
== [[image: pkg-block-logo.png||alt="pkg(5) logo"]] pkg(5): image packaging system == pkg(5), the image packaging system (IPS), is an attempt to design and implement a software delivery system with interaction with a network repository as its primary design goal. Other key ideas are: safe execution for zones and other installation contexts, use of ZFS for efficiency and rollback, preventing the introduction of incorrect or incomplete packages, and efficient use of bandwidth. === Reporting bugs === We would really like to eliminate any bug you encounter—so every bug report we receive is valued. Should you run into a bug, please report them on the discussion list. === Getting more involved === Our discussion alias is ''pkg-discuss AT''. Ideas, issues, patches are all welcome; commit notifications add to the open development aura. The [ TODO list] provides some potential areas to start; short essays and notes on various topics—such as [ content filtering], [ handling of ELF dependencies], and some [ initial RFEs]—can be found in the ''doc/'' directory of the repository. More specific hints can be found in the [[Developer Information|Developer Information Page]]. If you want to experiment, you can use the image-create subcommand of pkg(1) to create your own image that subscribes to the release/ repository: <pre name="sh">$ pkg image-create -F -p /path/to/image</pre> (If you're interested in developing pkg(5)-style packages, the best step at present is to join the discussion. As support for multiple package authors is fleshed out, we'll set up additional test publication spaces or repositories.) The source code is stored in a Mercurial repository here at You can get a copy of the source tree via: <pre name="sh">$ hg clone</pre> If you would like to browse the source directly, it's available via the source browser: :[] Please get a contributor agreement in place before submitting anything but the most trivial of patches. At present, pkg(5) is being implemented in Python; we're developing in an ON-sympathetic coding style. === Documentation and architecture process === Current official documentation is available [ here]. Also, you can read the draft manual pages directly out of the source code repository: * [ pkg(1)], the retrieval and installation client, * [ pkgsend(1)], the publication client, * [ pkgrecv(1)], the raw contents retrieval utility, * [ pkg.depotd(1M)], the depot server, and * [ pkg(5)], the system overview. The [ one pager], which begins the architectural review, was recently published; the image packaging system will be tracked as case 2008/190. === Background reading === The project team has been explaining some of the ingoing assumptions behind the project in a series of blog posts: * [ Bart] on [ ''Rethinking patching''], and * [ ''Stephen''] on [ ''Observations on packaging''], [ ''pkg(5): a no scripting zone''], [ ''pkg(5): leaving the build system `out'''], and [ ''pkg(5): no more installer magic''].
Please Confirm