Open datakurre opened 11 years ago
djay
commented
11 years ago I'm ok with this change but I've been thinking of a major change to how it works.
I've been experimenting in this branch https://github.com/collective/collective.hostout/tree/fabric_compat
datakurre
commented
11 years ago Thanks.
For me it seems that the new approach doesn't have effects on how plugins are included. (Only on how plugin fabfiles should be written.)
It might be also possible that my patch could also be applied for that branch without changes. I could make a separate pull request also for that branch.
datakurre
commented
11 years ago Ok. I didn't fully understand the fabric_compat-branch when I first looked at it. I need to find time to try it out.
So, merging this pull would make sense only, if there will be release of "old" hostout.
We started to use collective.hostout, because of its extensibility (re-usable fabric-files) and buildout-configuration (using buildout's extends/<= -feature a lot), but eventually ended with a completely different/overriding command set of hostout.pushdeploy and not using any of its built-in commands:
https://github.com/datakurre/hostout.pushdeploy
Yet, because hostout already separates it's built-in commands from everything else pretty well, we would not like to completely fork it.
Therefore, this feature request. I'm also open for other ways to implement this behavior.