Brock Pytlik wrote:
Tom Mueller wrote:
Brock Pytlik wrote:
There are three distinct entities, publishers, streams, and
repositories. Publishers are the entities who put together
distributions, sign packages, etc... Specifically, they distribute
one or more streams (or trains or whatever term we settle on. dev
and release are two examples of streams for the opensolaris.org
publisher.). Repositories are simply collections of packages,
possibly from multiple publishers and multiple streams from those
publishers.
About repositories - first, I'm assuming that there is a distinction
between a pkg.depotd process and a repository. A repository would be
identified by a unique URL, but a pkg.depotd process might eventually
service multiple repositories. Is that right?
No, I think we're suggesting moving to a model where there's a
one-to-one mapping between pkg.depotd process and a repository. But
that depo/repo/process might serve up packages from many streams and
many publishers.
Essentially, we want to move to a model where a repo/depo is just a
container that hands out bits of packages to clients as needed. In
short, the average user should never need to care what repo(s) they're
connected to.
So from a users standpoint instead of telling them about Publishers in
the main UI we would change this to something that couples Publishers
and Streams like:
Package Source: opensolaris.org-release
Package Source: opensolaris.org-contrib
Package Source: Sun-extra
In the Add Publishers the user would specify a URI for the Publisher,
but after that they really shouldn't be messing with a Repository URI as
this is just part of the internal plumbing a Publisher and its streams
are using. Is that right?
So in Manage Publishers, you would list Publishers and their streams, if
a stream was incompatible such as dev and release, we would need to flag
this to the user so they could choose which of these incompatible
streams to use, but in general the Publisher metadata will indicate what
should be the active streams by default and for the general users they
need never worry about having to choose them.
I assume all this rework is not targeted for 2010.02? If it is there's
going to be a lot of rework on the GUI side for the Add and Manage
Publishers and presumably on the CLI side as well.
JR
Does that make things clearer?
Brock
So assuming that a repository is identified by a unique URL (possible
with mirrors that are identified by other URLs), what would be an
example of where multiple streams would be served from a single
repository? Also, what would be an example of where packages from
multiple publishers would be coming from a single repository?
I'm wondering if the world would be simpler if we just chose to limit
a repository to containing packages from a single stream from a
single repository. This would make a 1:1 relationship between stream
and repository - effectively the two concepts are the same.
Thanks.
Tom
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
