[packages/rpm] - add filetriggers directory

[Jeffrey Johnson]

On Sep 12, 2012, at 2:32 PM, Jan Rękorajski wrote:

> On Wed, 12 Sep 2012, Elan Ruusamäe wrote:
> 
>> On 12.09.2012 14:51, baggins wrote:
>>> commit e9eb00afc48b027786d4fd5c23e6cff20acc8df8
>>> Author: Jan Rękorajski <baggins at pld-linux.org>
>>> Date:   Wed Sep 12 13:33:26 2012 +0200
>>> 
>>>     - add filetriggers directory
>> ...
>>> 
>>>  %dir /var/lib/rpm
>>> +%dir /var/lib/rpm/filetriggers
>> 
>> why filetriggers in /var/lib? due /usr separation? maybe put to /lib/rpm 
>> instead then? more FHS friendly imho
> 
> What about /etc/rpm/filetriggers ?

FYI: this is Mandriva filetriggers and is likely to be removed in favor of
using existing %trigger* scripts, which permit file paths, directory paths (with trailing /),
and glob expressions to be used.

The reason for _NOT_ using Mandriva file triggers is that %trigger scripts are
wholly contained within package metadata and so can be debugged more easily
than a pile of "stuff" that is read, matched, and run (and rpm is blamed when the
opaque "stuff" breaks).

Try-and-see: there's likely still a bit more to do, but the basics have been in place
with test cases for several years now.

> Let's try not to needlesly multiply directories.
> 

FYI: rpm-5.4.10 is already using /var/lib/wdj path for sqlite3 and (soon) libgit2 development.
And /var/cache/rpm is likely to be used for secondary indices and perhaps transactional
logs by end-of-year.

Reliability/performance is increased if the data store, the __db* cache, and the logs can
be put on different partitions/disks.

73 de Jeff