Hi.

gitolite3 can make use of Redis for caching (see
http://gitolite.com/gitolite/cache.html).
It needs the redis-server and the perl driver for this.

So perhaps gitolite3 should Suggest both (Recommending
them would definitely be too much, since only few users
will likely need this).

Cheers,
Chris.

Christoph Anton Mitterer <calestyo@scientia.net> writes:

I'm not completely convinced. Of course adding a suggests doesn't cost
much, but since the admin has to hand edit the config file anyway, I
think that

- installing redis is the easy part

- the convenience gained for the small number of people interested, is
  probably offset by the fact that just installing the package doesn't
  do anything.

Christoph Anton Mitterer <calestyo@scientia.net> writes:

I'm not completely convinced. Of course adding a suggests doesn't cost
much, but since the admin has to hand edit the config file anyway, I
think that

- installing redis is the easy part

- the convenience gained for the small number of people interested, is
  probably offset by the fact that just installing the package doesn't
  do anything.

I don't really have a strong opinion here.
That's clear :)
Well normally I think packages should try to express any possible
"dependencies",... and when they're so weak/rarely used as in this case
with gitolite3/redis, Suggests is the strongest appropriate
dependency... we already have quite often packages that suggest other
packages which they'd only use after further manual configuration is
done, so I don't think *this* is an argument against adding it.

As for the possible confusion that people might experience,... I
personally generally recommend that packages add information to their
package descriptions about Recommended/Suggested packages for which the
benefit/use case is not absolutely obvious.... e.g. as the devscripts
package does it (quite heavily).

So my recommendation would be:
Add it as Suggests + add information to the description what this would
be used for.


Best wishes,
Chris.