Closed (fixed)
Project:
Hostmaster (Aegir)
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
16 May 2012 at 18:05 UTC
Updated:
3 Sep 2015 at 14:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedYes, I think the Client feature is very tightly coupled into the entire system despite appearing as a separate 'feature'.
We either need to work out how to de-couple it - but I suspect the work involved might justify going the other way and preventing it from being disabled.
Comment #2
steven jones commentedI'd go for making the dependency explicit in 1.x, and then uncoupling them in 2.x.
Comment #3
steven jones commentedI've made the dependency explicit. i think removing the dependency will have to wait.
Comment #5
anarcat commentedComment #8
polWe can still disable the client module on Aegir 7.x-3.x.
When disabled, all the features gets disabled too.
Comment #9
polComment #11
gboudrias commentedAs far as I can tell this is all we're missing.
Comment #12
gboudrias commentedCan anyone review this simple patch so we can get this in 3.1?
Comment #13
ergonlogicThat should do it.
Comment #14
joestewart commentedCurious, does the sites directory symlink still work after this change?
http://cgit.drupalcode.org/provision/tree/platform/provision_drupal.drus...
Comment #15
gboudrias commentedHi Joe, not sure I understand your question, all the patch does is forbid people from disabling the module, so it shouldn't change the functionality at all. Can you elaborate?
Comment #16
joestewart commentedHa, I misread the patch. I thought the client feature had already become required. And this patch was allowing it to be optional again.
Ignore.
thanks.
Comment #17
gboudrias commentedForgot the pound sign in the commit, pushed in a0009f235ea8939018d537830a109c56c9eafff0.