By fuzzygroove on

Would anyone see a benefit in the creation of a module that automates the process of installing modules?

Every time i need to add a module I go about the the same process, and it seems like there is already a standard "packaging" that each module must adhere to, so why not automate this process with a module?

Almost all modules (that require more than drag-drop) include:

directory: /
db script: .mysql (sometimes a .pgsql --- this could be handled too)
module: .module
---
etc: some other stuff that I don't care about.

Anyone want to see an installation (and maybe even un-installation in the future) module?

-ian

Comments

fuzzygroove’s picture

fuzzygroove commented

directory: <module_name>/
db script: <module_name>.mysql (sometimes a .pgsql --- this could be handled too)
module: <module_name>.module
etc: some other stuff that I don't care about ("README"s, CSS, etc).

---
The thing ate my placeholders - now i need to submit a change request-- don't eat unmatched tags! should change <foo bar> to &lt;foo bar&gt;

signal9’s picture

signal9 commented

Seems as though that could become pretty unwieldy pretty quickly, particularly if something didn't happen quite the way it was supposed to--for example, a version mismatch or something. Also, I'm not sure what kind of controls are on how modules are installed, but it may be that there is room for variation there, and that could be pretty difficult to account for.

I know I wouldn't want to have to test it on every module that people release--every time they update. =)

--------------
Govorite po-russkij? Want to?
http://www.sobrania.net/russian/