Modman reverse

[waynetheisinger]

Hi Colin, I'm developing another feature on my fork which I'll do as a pull request when finished, I'm commenting here in case you or others have got comments whilst I'm writing the code.

Basically its a modman reverse function: The use case for this feature is for when you've been developing code in locations actually within your main Mage application rather than in a modman module, but you now decide you want to move the code into a modman module.

To use the new feature you simple need to write a modman file in an empty modman module (ie one that contains no files). You then call modman reverse modulename. Modman reads the modman file and copies all the contained paths into the modman module's folder from the main Mage directory.

[robert-blankenship]

This would be so awesome

[wayneintacart]

Hi Robert, when I actually started working on this I found it to be less useful than I expected. The reason? When writing the modman file you can't use bash auto completion unlike cp where you can, which results in less key strokes. So I found it was quicker to cp the paths and then use my modman automodman function to automatically write the modman file.

Let me know if you still think it might be useful and I might have another look

[robert-blankenship]

Ah I think I am following you. You're saying that it's less work to just copy files to .modman/module-name rather than write a modman file.

Okay, well for one, it's possible that the modman file exists (ie, new member of a team joins the project). Also, one typically has to write the modman file anyway.

Notwithstanding, mistakes can happen at the command line :). Just the other day, I almost nuked my dev Mage install.