[Pkg-graphite-maint] Dependency on graphite-carbon; lack of depend on python-whisper

[Dave Rawks]

On 01/10/2013 12:44 AM, Jonas Genannt wrote:
> Hello Dave,
>
>> 	I see that your control file includes graphite-carbon as a
>> dependency, which it shouldn't as it is possible to use graphite-web
>> on a separate box from where your carbon-cache instance is run.
>> However I think that graphite-web does depend on python-whisper's
>> whisper module. I've no idea how to propose a change or whether this
>
> so you think we should:
>
> Depend on: python-whisper AND python-ceres (Whisper replacement)
>
> Suggests on: graphite-carbon
>
> But since graphite-web needs filesystem access to the Whisper or Ceres
> files you need some shared filesystem.
>
> What are you using that Grpahite-Web can access Whisper files on the
> other server?
>
> The other solution is to install graphite-carbon and disable it in
> etc/default/graphite-carbon.

So that is exactly what I'm saying. You can install graphite-web and it 
can have access to whisper files by a shared filesystem or a process 
that copies them over for offline analysis etc... That said having 
graphite-web and carbon-cache installed on the same system is very 
common; graphite-carbon should definitely be suggested and the 
python-whisper package should be depended upon since it was previously 
only depended upon indirectly via the graphite-carbon dependency. As for 
the python-ceres dependency, only the current "trunk" branch of 
graphite-web and graphite-carbon depend on ceres which means inclusion 
of the dependency should be a non-issue until such time as the next 
major version is released, 0.10.x, which would presumably be tagged from 
trunk.

-Dave