RPMFILE_UNPATCHED is no more used and RPMFILE_EXCLUDE only exists during
spec parse (see rpm commit 8d277bbb)

Conflicts:
	NEWS
	URPM.xs

aka having @recommends@ lines instead of @suggests@ ones

Conflicts:
	NEWS
	URPM.xs

rpm-4.12.0 introduces a new weak deps implementation (the 3rd one to be
used in mdv/mga!)

The tag we used to use (RPMTAG_SUGGESTSNAME) is now OLDSUGGESTSNAME
=> we need to handle both old & new tags

Hopefully rpm-4.12.x enables to check both old & new tags when using
xxxNVRS variants

We thus have a choice between RECOMMEND & SUGGEST tags, that both
fallback on older SUGGESTS tags if no new ones are found.
The difference is that they filter old suggests depending on
RPMSENSE_STRONG hint.

As we used suggests in the recommends role, this is the perfect time to
switch from suggests to recommends
(with a patch on rpm in order to fallback RECOMMEND on weak (old)
SUGGESTS instead of on strong (old) ENHANCES as we didn't used the later
in mga)

Our rpm is patched so that RECOMMENDNAME fallbacks too.
In Suse, only RECOMMENDNEVRS is the only RECOMMEND variant that handle
the fallback on old tags.
However, using RPMTAG_RECOMMENDNEVRS makes URPM->suggest_nosense to
return versionated suggests, which while not supported by urpmi, do are
used by a couple packages (such as git or gnome-user-share)

This breaks urpmi as suggests on "foo >= x.y" is not interpreted by
urpmi which thinks that "foo" is a new suggests and reinstalls a
previously removed suggests
Hence we patched rpm.

Conflicts:
	NEWS
	URPM.xs

in order to access to extension tags such as new weak deps tags
(needed for next commit)