[email protected] wrote:
Shawn Walker wrote:
...
Ok. My plan is to have the transport make use of your new publisher objects for obtaining the correct information. I can live with purging the dead code as part of the transport re-write.
I've purged a bit more, but there is still plenty left (mostly centered around obtaining ssl credentials or mirror and origin information).
I'd like to leave this as is for now. My assumption was that with your transport putback, this would change anyway, but at least there would be a framework in place. At that point we could revisit this and determine what the best way is to deal with sorting. Is that agreeable?Perhaps we could find an acceptable compromise. Would you be willing to leave the sorting by priority order, but add an instance variable to the Repository class the named the sort policy. If you created a sort policy table that contains the different sort functions, listed by name, it would be fine if it had just the following right now: { "priority" : lambda obj: (obj.priority, obj.uri) } Would this work, or is that more change than you would like?
In the interest of the transport work, I'd be more than happy to add this. However, remember that none of this information is stored by the client right now because the cfg_cache file format currently isn't expressive enough. But that should change before the transport work gets putback, so will provide a nice segue.
Cheers, -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
