Brock Pytlik wrote:
Shawn Walker wrote:
[snip]
==============================
Proposed Server Storage Scheme
==============================
<REPO_ROOT>/
__catalog/
__index/
<publisher>/
file/
pkg/
<stem>/
<manifest-named-after-uri-encoded-version>
trans/
==============================
Proposed Client Storage Scheme
==============================
<IMG_ROOT>/
__cert/
__history/
__index/
__pm_cache/
__state/
<publisher>/
file/ (formerly download)
pkg/
<stem>/
<manifest-named-after-uri-encoded-version>
pkg_cache/
<stem>/
<uri-encoded-version>.<cache_name> (manifest cache file)
[snip]
If we're going to be making this change, let's look at what we'd need to
do so enable standing a depo up on the file structure of a client image.
The obvious thing that jumps out at me is that __state should probably
become __catalog (or the other way around) assuming that the catalog
info can be coerced from one to the other. Other than that, it seems
like everything matches up well.
Hmm. The state/known directory on the client is the equivalent to the
catalog/ directory on the server.
That just leaves state/installed, which has no real equivalent on the
server. I guess __installed/ then?
The other problem is that the image catalog contains additional
information that really shouldn't be shared with other clients (state
information about the package), so I don't know that we'd want to stand
up a depot server that way or use the image as a repository with the
catalog data in state/.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
