Shawn>> I always envisioned a 'depot' as a collection of one or more
Shawn>> repositories -- unfortunately, we ultimately decided having 'pkg.depotd'
Shawn>> serve more than one repository was likely to result in a very poor user
Shawn>> interface. Probably for the same reason you chose to have a separate
Shawn>> executable for this "new" service.
Yep, I struggled with the name too. I initially called it apache-depot, but
was then nervous about
a) using the Apache name at all (for trademark reasons)
b) potentially tying us to a single webserver implementation (hence the
currently redundant -t flag)
pkg.depot-scalable doesn't seem right, because it's making a promise about
scalability, which while probably well-founded for most cases, mightn't be
true given enough clients. (it feels almost as bad as calling something
'unbreakable' :)
pkg.depot-multi doesn't seem right either, but I can't explain why.
The current name pkg.depot-http also won't be right once we support https, so
I'm definitely happy to change it.
So with that in mind, can anyone suggest better names? I'm going to suggest
some here to get started.
How about simply application/pkg/depot? Or if we think we might
envision other "depot" services (for example, for cleanup) maybe
application/pkg/depot/server?
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
