should gdp recommends or depends on engine ?

[Alexandre Detiste]

(retitling because the recommends vs depends issue is much mor general/interresting)

> Incidentally, for Z-code games requiring Zoom, shouldn't the resulting 
> packages depend on zoom-player rather than just recommending it? I know 
> we usually just recommend engines, but I'm not sure that's always 
> appropriate.

This is not Z-code games specific at all.

I have no idea why all the data packages merely recommends the engines;
this was just already there in the shell-based G-D-P.

I wrote a bit about it here:
http://anonscm.debian.org/cgit/pkg-games/game-data-packager.git/commit/?id=718cd8a50835205dfe2ec1044f5929db2c7fc45b

    # We only 'recommends' & not 'depends'; to avoid
    # that GDP-generated packages get removed
    # if engine goes through some gcc/png/ffmpeg/... migration
    # and must be temporarily removed.
    # It's not like 'apt-get install ...' can revert this removal;
    # user may need to dig again for the original media....

but, as an aftersight, this seems only applicable for the users
following/pinning from unstable; users of testing/stable would
never have to remove engines.

So I guess we needed to balance all the pros & cons again.

If the engine is not yet packaged & users may wnat to run the binary from the git tree:
  -> only recommends

Likewise for a G-D-P backport to Jessie
  -> recommends engines that were not yet packaged then

other cases:
  -> depends on engine


For .rpm file generation I originaly settled on "Requires:" (= Depends) and
I'm waiting to get complaints to chage it to Recommends.

Alexandre