2008/5/29 Stephen Hahn <[EMAIL PROTECTED]>: > * Nicolas Williams <[EMAIL PROTECTED]> [2008-05-29 21:14]: >> For pkg URLs we might actually want: >> >> pkg:<URL> >> >> i.e., something like: >> >> pkg:http://<repository-server[:port]>/<pkg-URI-reference> >> >> e.g., >> >> pkg:http://foo.example/opensolaris.org/solaris/make >> >> More specifically, I'm proposing these syntaxes: >> >> URN --> pkg:///<vendor>/<pkg-name> >> URL --> pkg://<location>/<vendor>/<pkg-name> >> +-> pkg:<URL> where <URL> contains a pkg URN reference >> >> Plus versions, hashes and signature fingerprints as URI fragments: >> >> pkg:///<vendor>/<pkg-name>#<version> >> pkg:///<vendor>/<pkg-name>#<hash> >> pkg:///<vendor>/<pkg-name>#<signature fingerprint> >> ... >> >> and public key/certificate fingerprints as vendors: >> >> pkg:///<pubkey or cert fp>/<pkg-name> >> >> and even: >> >> pkg:///<pubkey or cert fp>/<hash> >> >> The URN reference parts should be opaque to clients, but when used in >> the <vendor>/<pkg-name> form they can convey some information to human >> users. >> >> Servers should be able to find packages by all of their URN reference >> aliases. (I.e., by name, name and version, by hash, ...) > > The image configuration already (and deliberately) abstracts out > specific servers and will do so for retrieval policies. A -s > option to allow a one-time override is possible. Otherwise, I'm not > interested in going down this path.
A -s option to the client for any operation? I've been considering implementing: pkg -s file:///path_to_repo Correct? -- Shawn Walker "To err is human -- and to blame it on a computer is even more so." - Robert Orben _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
