plugin: Don't do lossy shift on hash
plugin: Don't do lossy shift on hash

In plugin is responsible for calculating a hash of the dependencies
in order to determine if the cache should be invalidated or not.
Currently, the hash combining method removes a bit of the original
have before combining with an addition. As we use 32bits for our hash
and shift 1 bit for each file and directory, that resulting hash only
account for the last 32 files. And is more affected by the last file.

Rotating technique (shifting, and adding back the ending bit), can be
use to make the addition non-commutative. In a way that different order
gives different hashes. In this case, I don't preserve this behaviour
because the order in which the files are provided by the OS is
irrelevant.

In most cases, the XOR operation is used to combine hashes. In this
code we use the addition. I decided to preserve the addition because
we make use of non-random hash ((guint) -1) in the algorithm for
matching files that are not really part of the hash (symlinks, special
files). Doing successive XOR on this value, will simply switch from
full ones, to full zero. The XOR used with whitelist has been preserved
as it's based on a fairly randomized hash (g_str_hash).

https://bugzilla.gnome.org/show_bug.cgi?id=758078

jpxiong/gstreamer,StreamUtils/gstreamer,StreamUtils/gstreamer,centricular/gstreamer,jpxiong/gstreamer,centricular/gstreamer,jpxiong/gstreamer,centricular/gstreamer,StreamUtils/gstreamer,StreamUtils/gstreamer,jpxiong/gstreamer,centricular/gstreamer,jpxiong/gstreamer,centricular/gstreamer,StreamUtils/gstreamer