I think I'm starting to understand your intended relationship between publishers and repositories. Shouldn't a repository know what it's publisher is? If it already does, why doesn't pkg just assign the right publisher name when a repo is added to the list? Unless all a publisher's repos will get automatically added, it seems like you'd want the pkg command to be "add repo" instead of "add publisher", and the publisher name for each repo gets automatically figured out, and the repos get combined together under each publisher.
Does any of that jive with the direction you're going in? Or am I still confused? --chris Shawn Walker wrote: > Chris Quenelle wrote: >> Shawn Walker wrote: >>> Long-term, this will all be made much clearer, in the meantime, this >>> might help: >>> >>> http://blogs.sun.com/srw/entry/what_s_in_a_name >> >> Well it's good that we recognize there is a problem. :-) >> >> From your blog it sounds like someone who wants to publish packages must >> have their own domain or subdomain. Doesn't that exclude a lot of >> people >> who would otherwise have no trouble running a server, and making it >> available >> at a specific URL? > > Not quite. > >> So you seem to be saying: >> A publisher is a domain name (forward or reverse) > > Yes. > >> A repository is a group of URIs > > Not quite: > > http://cr.opensolaris.org/~swalker/pkg-5299/src/man/pkg.1.txt.wdiff.html > > A publisher is a forward or reverse domain name (e.g. > "opensolaris.org" or "org.opensolaris") that can be used to identify > a person, group of persons, or an organization as the source of one or > more packages. The name of a publisher does not have to be contained > within the URIs that identify the locations of publisher > repositories. For example, the name of a publisher might be > "example.com", but its repositories may be hosted at "example.org" or > "example.net". > > A repository is a location where clients can publish and retrieve > package content (files contained within the package such as programs, > documents, etc.) and metadata (information about the package such as > its name, description, etc.). As an example, a publisher named > "example.org" may have their repository located at the URI > "http://example.org/repository";. > >> This doesn't seem to map very clearly onto the implementation of pkg >> where: >> A publisher is a random user-assigned name. (like "osol-dev") > > Currently it is user assigned, but in the near future, users will not > be allowed to set the name; the repository will provide it. > > Users will be allowed to provide an 'alias'. > > The other part of the confusion here is that the cli interface needs > some reworking, as well as the packagemanager GUI to better delineate > these concepts. > >> A repository is understood to be a single specific URI. (like >> http://pkg.opensolaris.org/dev) > > Correct. > >> It seems useful to expand on your blog entry with a more careful >> specification >> before proceeding with the documentation. > > See above. > >> As a side note, what possible use is a domain name that can be either >> forward >> or reverse? It's not possible to automatically map it onto a URI. > > I just took the original definition found here from Stephen's initial > proposal: > http://markmail.org/message/dfrx6reopkm2umeg > > It is not intended that you necessarily be able to map it to a URI > though that would be convenient. > >> What are the benefits of creating the concept of a "publisher"? If >> there is >> no formalism around registration or identification? At the level of >> packaging >> technology it seems that defining the concept of "repository" as all you >> need to do. > > The problem is that the rest of the structure hanging off this hasn't > been implemented yet. As I understand it, the publisher name will > also represent an identity that will be used to cryptographically > sign packages. > > Though I could be wrong about all of this :) > > Stephen or Bart are the most likely to know. > > Cheers, _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
