My specific use-case is that I want to hide the default drupal installation profiles on the site creation form.
I only want my admins to be able to install a very specific set of install profiles, and having an extra profile (or 3) is just confusing.

In general, I can see that it might be useful in general to disable specific packages (modules, themes, profiles) on a per-platform basis.
Is this something that other folks could use too?
Is this something that maintainers would consider including in hostmaster, or must this be relegated to contrib?
I would be willing to work on a patch, but I won't waste my time if it will never get into the package.

Comments

AaronBauman’s picture

FWIW:
digging into this, I see that it's possible to achieve this behavior by unpublishing the package node, but there's no way to do this through the UI. caveat: i'm not certain whether the node status will be respected, or could be reverted to published during a verify action.

anarcat’s picture

Unpublishing the node sounds like a great idea, and it should be fairly easy to make verify respect those settings.

Can you confirm unpublishing this actually works?

AaronBauman’s picture

Status: Active » Postponed

actually, unpublishing seems to have had some unintended, negative consequences.
for my case, i was able to lock the platforms to significantly reduce the number of options.

i'll change this to postponed, since my particular issue is more or less solved.

ergonlogic’s picture

Version: 6.x-1.x-dev » 7.x-3.x-dev
Issue summary: View changes

New features need to be implemented in Aegir 3.x, then we can consider back-porting to Aegir 2.x. Aegir 1.x is essentially deprecated.