Re: Plan to remove ruby-fog meta package and its leaf dependencies

[Pirate Praveen <praveen@onenetbeyond.org>]

On ചൊ, ഡിസം 25, 2018 at 8:22 വൈകു, Pirate Praveen 
<praveen@onenetbeyond.org> wrote:
> Hi,
>
> We started maintaining a lot of fog modules because diaspora and
> ruby-asset-sync declared dependency on ruby-fog, now both declare
> dependency on ruby-fog-core and the modules that they really want. So
> I'm proposing we remove ruby-fog and the following modules which does
> not have any other reverse dependencies.

diaspora 0.7 is in unstable now and I have filed removal request for 
ruby-fog now. I will be filing removal requests for them soon.

> If any of you want to continue maintaining these, please speak up now.
>
> Keeping them would mean, we keep updating them during transitions, for
> example now ruby-fog-core update need to take care of all these 
> reverse
> dependencies.
>
> ruby-fog
> ruby-fog-atmos
> ruby-fog-azure
> ruby-fog-brightbox
> ruby-fog-cloudatcost
> ruby-fog-ecloud
> ruby-fog-powerdns
> ruby-fog-profitbricks
> ruby-fog-riakcs
> ruby-fog-sakuracloud
> ruby-fog-serverlove
> ruby-fog-softlayer
> ruby-fog-storm-on-demand
> ruby-fog-terremark
> ruby-fog-vmfusion
> ruby-fog-voxel
> ruby-fog-vsphere
> ruby-fog-xenserver
>
> Thanks
> Praveen