On 05/19/10 04:57 PM, Stephen Hahn wrote:
* Shawn Walker<[email protected]> [2010-05-19 14:42]:
On 05/18/10 06:00 PM, Stephen Hahn wrote:
* Shawn Walker<[email protected]> [2010-05-18 15:43]:
...
Could you be more explicit about what you mean by this? I don't
quite connect this to section 5.1's text.
I was hoping that
pkg install -g http://example.com/foo.p5p
would work.
To clearly set expectations, are you expecting:
pkg install<uri_to>/foo.p5p
...to automatically attempt to install any packages named within?
While:
pkg install -g<uri_to>/foo.p5p
...simply uses foo.p5p as a source of package data and requires that
you specify package(s) to install?
Actually, I just want to know what
# pkg install -g<uri_to>/foo.p5p
does by default?
I had assumed it would do the same thing we do now when you don't
provide a package FMRI:
$ pkg install -g <uri_to>/foo.p5p
pkg install: at least one package name required
Try `pkg --help or -?' for more information.
As a related question, how do I see the contents of
a .p5p file from the command line. (Zero points for "cat foo.p5p"...)
What about 'bobcat foo.p5p'? :)
If you're speaking of the list of packages in the archive, this is
covered in section 5.4, although I had originally required the -g option
there. If I apply the input analysis process you suggested earlier,
that would be simplified instead to:
$ pkg list <uri_or_path_to>/foo.p5p
NAME (PUBLISHER) VERSION STATE UFOXI
foo 1.0-0.133 known -----
...
$ pkg info <uri_or_path_to>/foo.p5p
Name: package/pkg
...
If you're speaking of the raw contents (files) in the .p5p, then:
$ tar tf <path_to>/foo.p5p
pkg5.index.0.0.gz
catalog/
...
(sun tar, gnu tar, star, etc. all work...)
Cheers,
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
