Custom module information missing in drupal-org.make file [#2227983]

Hi,

I have one suggestion regarding drupal-org.make file. I did not find better place to add my findings so I am sharing the same here. If I have some custom modules in my distribution then how can I include the information regarding these in drush-org.make file. I know because these modules not exist on drupal.org so there is no meaning to add any information in drush-org.make file. Now the question raise suppose I have to contribute this distribution on drupal.org including these custom modules then how I will include these custom modules in distribution. Because after running Profiler Builder module, I'll get information regarding contributed projects like modules, themes and libraries.

I did lot of research on same but no where found solution of this due to lack of proper documentation of same. It will be great if we add some information here regarding this type of scenario. Most of the time we face this scenario because there can be number of custom projects that are still under sandbox or not even on sandbox. For this I have followed the given steps :

Suppose my distribution name is foo then Profiler Builder module generate following files for us by default:

drupal-org.make
foo.make.example
foo.info
foo.install
foo.profile

Now I did some manual task here:

Step 1: I gone through foo.make.example file and look for ; +++++ TODO modules without versions +++++.
Step 2: I included these without versions module and modules that are not published on drupal.org, in same directory inside custom folder.
Step 3: I created build.sh file and did the required changes in this. We can copy this file from any existing distribution available on drupal.org.
Step 4: Now you are done with this and you can contribute your distribution on drupal.org including your custom modules.

I hope this will help for someone who are still looking for inclusion of custom projects in distribution.

Comments

Comment #1

btopro CreditAttribution: btopro commented 10 April 2014 at 18:59

Version:	7.x-1.0	» 7.x-1.x-dev
Status:	Active	» Needs review

1st off, always use dev of this module (marking dev). You should look in the local.make.example file for your custom modules not on d.o.. For those that you add to d.o. in a distribution / installation profile, yes, it will (may) incorrectly find these and attempt to tell you to download them. There are api hooks for removing these but I also think that if you group them under the project namespace of your distribution then it'll get rid of those from the build. Or, like you said, just delete those few and you'll still be good to go.

I'll accept patches to help resolve / streamline this stuff but I think you are right in just marking this as documentation and putting it here for others to search and find the steps to deployment.