<div class="gmail_quote">On Thu, Apr 16, 2009 at 8:16 PM, Robby Workman <span dir="ltr"><<a href="mailto:rw@rlworkman.net">rw@rlworkman.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, 16 Apr 2009 05:52:43 -0500 alkos333 <<a href="mailto:me@alkos333.net">me@alkos333.net</a>> wrote:<br><div class="im">
<br>
</div><div class="im">> On Thu, Apr 16, 2009 at 4:10 AM, Mauro Giachero wrote:<br>
> > Anyway, why a single queue? I think storing one queue per<br>
> > (relevant) package would be far more flexible, given that sbopkg<br>
> > makes loading and merging multiple queue files really easy. And of<br>
> > course, somebody could also build up a queue archive.<br>
><br>
</div><div class="im">> I know it' snot as easy as it looks, but it's doable. �One file<br>
> because I don't have to worry about merging them and running several<br>
> files. �I can just load one and tell it to run through the entire<br>
> thing. �Works like a charm here :)<br>
<br>
</div>Maybe I'm not fully understanding the goal here, but what if sbopkg<br>
were able to treat a queue as a package? �IOW, you would be able to do<br>
something like this:<br>
<br>
queue_all=queue1,queue2,queue3,...</blockquote><div><br></div></div>Being able to do this kind of thing has puzzled me for some time (despite me being probably the only sbopkg user not using saved queues).<br>The problematic side here is being able to actually manage (e.g. create) such queue. sbopkg code assumes that a queue is a flat list of packages, and changing it to manage a nested structure is far from easy :-/.<br>
<br>-- <br>Mauro Giachero<br>