Re: Protecting user changes in developer scripts handled files
>>"Adam" == Adam Heath <firstname.lastname@example.org> writes:
Adam> You may want to handle updates to this file the same way dpkg
Adam> does. During long operations, updates go into a .d style dir,
Adam> one update per file(sequential name). Then, at the end, all
Adam> those files are merged back to the main file.
How can one ensure that a script is run ``at the end''? This
seems prime candidate for the much talked about dpkg hooks, but those
are not yet implemented.
It would be nice to be able to break processing into parts,
but short of a cron job or something, unless there is dpkg support
that I am unaware of, this is hard to do.
A newspaper is a circulating library with high blood
pressure. Arthure "Bugs" Baer
Manoj Srivastava <email@example.com> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C