Rather than submit change after change to repository while developing, you can just reference your packaged profile/make file in a local directory.

core = 6.x
projects[] =  drupal
projects[xfortybase][type] = "profile"
projects[xfortybase][download][type] = "local"
projects[xfortybase][download][url] = "/home/pearcec/Documents/xforty/AEgir/xfortybase"
CommentFileSizeAuthor
drush_make.utilities.inc-local.patch785 bytespearcec

Comments

yhahn’s picture

yhahn commented
Status: Needs review » Closed (won't fix)

Working under the assumption that a makefile is a portable set of directives, a `local` option is basically 100% non-portable. Your makefile becomes specific to your file system and I'm not sure this is something we should support or in the spirit of the project.

Can you say a little bit more about your use case and what dev problem you're trying to solve with it specifically?

pearcec’s picture

pearcec commented

Every time I run drush make I need to check in my changes to my profile. This patch lets me point it at my local check out. I can make changes then run drush make again and again until I am happy the profile does what I want. Then I just check it in for good. Just seems more convenient and a better practice.

How do you develop changes to your profiles? Perhaps I am missing something.

cthiebault’s picture

cthiebault commented

I have the same problem. I'm developing a project that looks like:

myproject
    /modules
        /mymodule_1
        /mymodule_2
     /themes
         /theme_1
     myproject.profile
     myproject.info
     myproject.install
     myproject.make

Each time I want to run and test my code, I need to copy my modules, theme and profile (with a Makefile) to the drupal distro built by drush make.
All these files are under SVN so it's seems portable to me...
Is this a valid use case for the use of local files in the .make file?

Thanks :)