perhaps it offends some elegance, but why not ship with a <profilename>.module and its own install. you are bootstrapped there and can run wild. That's what I'm doing now with a profilename_setup.module. So it's not a huge deal as it does keep the .profile clean this way. So if there is a intent to keep profilename_install() simple and restricted then I'm fine with that, but wanted to bring it up to see if there was a good reason for it not working the way I thought it should.
Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob@electronicinsight.com Moshe Weitzman wrote:
Rob Barreca wrote:
My overriding of story in myprofile.profile hasn't worked yet Yeah, I really think we need to have a full bootstrap in profilename_install()...or profilename_enable() if we want to be consistent with how .install files are doing this now.
perhaps it offends some elegance, but why not ship with a <profilename>.module and its own install. you are bootstrapped there and can run wild.