On Fri, Dec 22, 2006 at 01:33:14PM -0600, Jason L Tibbitts III wrote:
>>>>> "AT" == Axel Thimm
<Axel.Thimm(a)ATrpms.net> writes:
AT> I'd prefer that over 3) because if you have a folder inotify a
AT> daemon you'd be running the updating again several times per
AT> larger rpm transaction. Unless that daemon would have a wait
AT> timeout on inotifies to collect several triggers, but then it
AT> sounds easier to do 4)
Besides, how do you then update the cache during, say, the initial
install, or if I install some packages in single-user mode?
Hopefully the installer won't have to start a pile of daemons just to
get a proper system.
I have to wonder, are the people who advocate keeping a daemon running
forever to keep things in sync over a one-line crontab the same ones
who oppose xdg-utils because it's a shell script of moderate length?
Because if so, there seems to be a significant disconnect there and
I'm having trouble figuring out what the rules are.
I wasn't thinking of forking daemons for the on-the-fly cache
updating, more a side effect of using gtk libs, e.g. a model like
python creating pyc on the fly, tex creating fonts etc.
--
Axel.Thimm at
ATrpms.net