Folks, We have feedback from marketing and xDesign who'd like to see Mimetype support added so on a Web server with the mime type appropriately configured a user could just click on a link to a suitable file of the given mimetype and have PM launched on the client to add an authority (if not already registered) and install one or more packages if specified in the file.
Stephen has posted about the authority/0 action against a depot server that would return authority info to allow a client to setup and configure the authority. In the form of the standalone document format, I'd like to extend this to allow packages to be included for install. Suggested Mimetype to cover both authority and package installs (changed from pkg-auth and .pkgauth): Mimetype: application/vnd.opensolaris.pkg-info Suffix: .pkginfo We have modified SUNWips-gui package to handle the mimetype registration on the desktop in conjunction with the desktop-mime-cache service. Currently we have a prototype working with the basic configuration file format supported by ConfigPasrser, as this met the needs of the prototype, but are happy to change over to any suggested format that has Python support. Stephen mentioned that Shawn has been looking at JSON support and we'd have no problems switching over to that. The prototype demonstrates mime type support allowing both an authority to be added (if not already registered) and one or more packages from the authority to be installed using PM. We would need to agree on a File format for the .pkginfo file. .pkginfo supported fields from Stephens authority/0 mail: ------------------------------------------------------------------------ authority_name: Required authority_fullname: Optional repository_nickname: Optional collection_type: "complete" or "supplement". Required. origin_urls: one or more Required. related_origin_urls: Optional mirrors: one or more, Optional update_period: Optional license_url: Optional. registration_url: Optional registration_protocol: Optional pkg_names: list of package names to install from this authority, the PM supports install of the latest package so only the package name is required at present, do we want/ need to support full fmri's here?? Optional <-- Only additional field we need at present Any thoughts? JR _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
