"Barry A. Warsaw" <bwarsaw(a)cnri.reston.va.us> writes:
I can sympathize with both reasons. However, the error message that
occurs when pui-list-packages is run isn't too helpful for someone who
might be less experienced.
It just bombs out saying
No remote package sites specified in `package-get-remote'.
What version are you running? This message appears nowhere in my
version (which is THE version for the package code currently) and CVS
tells me that version is also in 21.0.62
What you should get (and that is what happens here) is normal
*Packages* buffer with additional text on top reading:
===
Warning: No download sites specified. Package index may be out of date.
If you intend to install packages, specify download sites first.
===
Okay, how do know where to set this to?
I had hoped that the above would be enough to use the "add download
site" menu item. Somebody still needs to write customize magic for
package-get-remote so that it will offer values from
package-get-download-sites as suggestions. Then we can add
text/hyperlink to customize-variable package get remote. Unfortunately
this will not happen before 21.0 is released.
I apologize ;-). What might be useful however is, once you've
got a
bunch of mirrors lined up, you could pre-load this variable with those
sites, and do a random pick of a mirror from those choices.
Picking a random mirror is bad as connections from here to australia
are likely to be slow.
As for not going remote unintentionally, you could show some message
in the pui-list-packages buffer and have a single boolean custom
variable that says "go-remote?".
I was/am hoping that with a good custom framework around
package-get-remote adding another variable (a meta one) would be
unnecessary.
Jan