On 05/23/12 12:01 PM, Shawn Walker wrote:
On 05/22/12 16:15, Tim Foster wrote:
I've asked Danek to respond to this, but here's my primary issue:
* I don't believe that most users are going to want to manage multiple
versions of the same origin
That's a fair assertion, and if users don't want to manage multiple
versions of the same origin, then they don't have to. They simply need
to not add those multiple versions of a given origin. I suspect the
majority of users will not have multiple origins with different proxy
values.
That is, I don't believe it's useful to support multiple proxies for a
single origin, and even if we can, I don't think the user wants to
manage each one of those as separate origins.
The same goes for Key/Cert pairs.
So then behind the scenes we have multiple origins, and we just don't
show the user? That seems even worse.
Alternatively, trying to treat origin-properties (say key/cert pairs) as
being attached to a single origin, we'll have to redesign parts of the
transport to try each combination of URI + that property,
URI + (key/cert pair A)
URI + (key/cert pair B)
URI + (key/cert pair C)
etc.
and somehow track the corresponding statistics along the way. I'm still
not convinced that would be the correct approach.
I believe that when a user asks us to remove an origin without
qualifying it; they mean just that -- remove the origin and any references.
If they want to remove just a specific proxy or key/cert pair, then they
should specify the origin and the specific proxy or key/cert pair.
Alright, so this could be a simple user-interface change on my part. I
could make:
# pkg set-publisher -G http://foo bar
delete all instances of http://foo (ie. preserve the current behaviour)
and also make:
# pkg set-publisher -G http://foo --proxy None bar
delete the direct path to the URI, and have:
# pkg set-publisher -G http://foo --proxy http://baz bar
delete the proxied path to the URI. Likewise for API calls where users
don't specify the 'None' keyword for proxies, we delete all matching
origins for that URI.
That would preserve the current behaviour, but allow flexibility when we
need it.
I believe that in the user's mind, the origin only exists once; the
additional things are just that -- additional configuration for that
specific origin.
Again, this is the assumption I'm trying to challenge.
With that in mind, I also don't think we should present the same origin
multiple times to the user in the output of 'pkg publisher'. I think
that would be very confusing.
I added the "P" column specifically to disambiguate here.
To the user, they've told us where we can get packages, and how to reach
them. Viewing it as a "transport-path pair" seems very developer-centric.
I'd have thought that's just the sort of detail a system administrator
would appreciate. Certainly way better than having proxy configuration
squirreled away in a mish-mash of $HTTP_PROXY and $NO_PROXY environment
variables.
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
