Hi Krister. On Fri, 2009-05-01 at 16:38 -0700, [email protected] wrote: [...] > Where do you install your package content from? We've configured a > number of on-SWAN mirrors throughout the world, but I don't know if > there's one in your area. One possibility might be to setup a mirror in > your neighborhood. You wouldn't have to wait so long for downloads in > that case.
Well, it's not *that* long. :-) Admittedly I tend to upgrade to the next dev build as soon as I see the release announcement so I suspect I'm just hitting the servers at the same time everyone else is. :-) But I happen to be in New Hampshire, so if you have a greater Boston area mirror, that would be cool. I looked around at opensolaris.org but didn't see a list of mirrors for pkg.opensolaris.org. If you have a link, that would be great. Thanks! All of this said, the repo that's timing out is sunfreeware.com; not an opensolaris.org server or mirror. Besides... A good part of this is admittedly a philosophical/design argument -- food for thought, if you will -- and not a server issue or a complaint or anything else. :-) When I download files in a browser or ftp client, when I transfer files in a file manager, when I check my email, when someone is sending me a file via IM, when I perform just about any task that has the potential to take more than a few seconds and/or timeout due to a connection failure, there's a Cancel button of some sort. In other words, as a user I can always gracefully bail out of these tasks using the functionality provided to me by the app in question. Why is this not the case when I'm trying to add a repository that doesn't want to respond in a timely fashion? I shouldn't have to do a force quit of packagemanager IMHO. John's fix works nicely and makes the interaction with packagemanager a lot more clear given the conditions in question. (Thanks John!!) And I was going to just let this issue be. But when I saw y'all discussing the overriding of variables, it struck me that what you were discussing might not be necessary -- or ideal?? If the user of the gui is given a way within the app to gracefully bail when faced with a non-responsive repo, is there still a need for the gui to override PKG_CLIENT_TIMEOUT and/or PKG_TIMEOUT_MAX (checking first to ensure that the user hasn't created his/her own environment variable)? [snip] > Getting your > data from a nearby mirror might improve your download speed today, > assuming you're not doing that already. It's not the download speed, and I've no complaints about the performance, which has already improved significantly since 2008.11. My sincerest apologies if anything I said suggested otherwise. I just want the ability to gracefully bail out of things within the gui rather than having to wait for those things to timeout -- on the very, very rare occasions when they do. :-) Thanks and take care. --joanie _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
