>> Bet one needs two wwwoffle.conf's to do that. Andrew> That is indeed a suitable solution. It does what you want to do and Andrew> is simple to implement.
Well, two wwwoffle.conf's is no fun from the users point of view. One 500 lines long, the other 501. Only one of them will get updated by the updater script upon upgrade, at least here on Debian. One also needs say a wwwoffle.conf.master and a Makefile to produce the two different versions of wwwoffle.conf. Perhaps things could be easier if we could at any time do minute adjustments like $ echo bla > /proc/bla/bla can. Anyway, still need finer control for > I want to block new ... coming in when I'm online, but still be able > to 'enjoy' previously cached ones when offline Some kind of dontget-doesnt-apply-offline=true #but then the old functionality can #only be had by deleting pages one never wants to see but still wants #kept cashed just in case. >> Also I want a way to get one anyway, perhaps wwwoffle -g, despite my block. Andrew> If you have blocked it then it is blocked; this is what the blocking Andrew> options do. If you change your mind and want to get it then you will Andrew> need to unblock it. hmmm, perhaps a -gg or a minus-g-overrides-dontget=true #but then to #what depth? Anyway, "customers see need for more flexibility beyond monolithic DontGet".
