Brock Pytlik wrote:
What does "a depot hosting multiple repositories" mean to you? My
interpretation of that is that a single depot could contain packages
from different publishers, and likely both the dev and release. So, to
map this onto new terminology, a single depot can have multiple streams
from multiple publishers, exactly what's been proposed.
Actually, I've tried to clarify this multiple times, so for everyone
involved:
* a depot is simply a server that offers a collection of repositories;
(call the analogy police for the next part ...) I liken a package depot
to a train station, where the repositories (trains) are available :)
* Clients don't access depots (bear with me) for package data; they
access repositories -- which have specific locations. The fact that a
depot exists is invisible to a user, and is purely a provisioning detail.
How many type of URIs are there that a user needs to know about. Some
of the responses have talked about URIs for a publisher. What would
such a URL look like? For example, for OpenSolaris.org, would the
publisher URI be http://pkg.opensolaris.org/. And when this is
accessed, do you get a p5i file that has the list of streams and the
URIs for the repositories for those streams? For example,
http://pkg.opensolaris.org/release and
http://pkg.opensolaris.org/dev. Are those URIs for streams or
repositories? If a repository is hosting many streams and/or many
publishers, what are the various URIs for those?
In the new world? One. The publisher URI is all that a user will need to
know about. Streams don't have URI's. Depots have URI's. which the user
need never know about. So, I imagine it working something like this: The
user adds pkg.opensolaris.org, that sends back the information (likely a
p5i file, but again that's implementation details not relevant for a UI
discussion since the user will never interact with it) need to identify
p.o.o/repo as a default depo for this publisher. A repo has a single
URI. Streams do not have URIs. A publisher has a single URI which is
entirely distinct from any repo URI's it may suggest. For example, the
publisher foo.com might point a user at a repo at bar.org.
Close, but I'd say that repositories have URIs, and depots aren't even
in the picture. For the purposes of this discussion, replace depot with
repository and pretend depot doesn't exist 8)
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
