the only method drush_make currently has to discover it's context is recursion, ie, it knows it's dealing with a profile because it recursed into it to find the .make file.

this is bad, because sometimes you might want to run the .make file from the profile directly, and drush_make has no way of knowing it's in a profile.

therefore, i propose the addition of a new attribute:

type = profile

we could call it context, but i think type would make more sense to most people.

for extra bonus points, we could also offer a command line switch, which would make the order: command line trumps .make file attribute trumps recursion.

CommentFileSizeAuthor
#2 drush_make_any_core.diff1.36 KBadrian

Comments

adrian’s picture

adrian commented

we should also take advantage of the idea of building modules on their own.

so modules can have makefiles, such as the wysiwyg modules.

adrian’s picture

adrian commented
Status: Active » Needs work
StatusFileSize
new drush_make_any_core.diff1.36 KB

I was playing around with it, and i have a mechanism here where you can declare any project type as 'core' and it will use that as the base of your build.

I used it with the following makefile : 

core = 6.x

projects[hostmaster][type] = "core"
projects[hostmaster][download][type] = "git"
projects[hostmaster][download][url] = "git://git.aegirproject.org/hostmaster.git"

I had to modify the recursion code to pick up makefiles for core projects, and set the build_path correctly.

When you use --tar, this will also create a profile only tarball for you.

dmitrig01’s picture

dmitrig01 commented
Status: Needs work » Closed (works as designed)

you can change --contrib-destination. we worked this out in IRC