update for-next-release

This commit is contained in:
chess.griffin 2009-01-22 03:51:43 +00:00
parent 3e5420981c
commit d02f7d8ab7

View file

@ -32,6 +32,13 @@ source. Along these lines, one user mentioned that when this happened, the
item that failed the download was skipped when the user aborted the queue and
reran it. I could not reproduce this, but need to check it out.
Would it be helpful to have a way to run a queue through the update function?
Suppose you have a saved queue with several deps and a final pkg, and some of those
deps have been updated in the repo but the saved queue has older versions. If
the queue is processed, it will automatically pick up the newer versions, but
that is only for building and those changes are not 'saved' to the queue.
Maybe it would be helpful to be able to update a queue (but not run it).
Maybe standardize all the "Done" type dialogs. Perhaps create a simple
function that displays "Done" (similar to the empty_queue function) and then
call the function whenever a "Done" message is needed. We could even set it