I created a patch file to make a few changes to the Drupal core .htaccess file that are needed for my hosting environment, though drush make seems to not want to patch that file. I have successfully patched modules using patch files located at the same URL, so it doesn't seem to be an issue of the patch file not being accessible by drush make.
My patch file looks roughly like this:
Index: .htaccess
=============================================================================
--- .htaccess (revision 2)
+++ .htaccess (working copy)
@@ -11,7 +11,8 @@
Options -Indexes
# Follow symbolic links in this directory.
-Options +FollowSymLinks
+# This is disabled
+# Options +FollowSymLinks
# Make Drupal handle any 404 errors.
ErrorDocument 404 /index.php
@@ -56,6 +57,8 @@
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_value mbstring.encoding_translation 0
+ # Increased default memory limit
+ php_value memory_limit 48M
</IfModule>
# Requires mod_expires to be enabled.
and my makefile looks roughly like this (hostname of patch location removed, sorry):
core = 6.x
projects[drupal][patch][] = "http://path/to/drupal_patches/drupal_htaccess.patch"
Appreciate any help.
Thanks,
Paul
Comments
Comment #1
pfg commentedComment #2
dmitrig01 commentedTry patching core with a different patch. Is it that patching core doesn't work at all? Also, please post the output of running with --debug.
Comment #3
pfg commentedRunning with --debug showed nothing related to the .htaccess patch. It looks like it was ignored.
I will try patching core with a different patch tomorrow if I get a chance.
Is there any documentation yet on the flags (such as --debug) for drush make?
Comment #4
wik commentedSame problem here:
Patches works fine for modules, but seems ignored for drupal core.
Thanks.
Comment #5
dmitrig01 commentedFixed in latest dev release.
Comment #7
grendzy commentedI'm not sure if this is by design, but patches aren't applied if you use the recursive feature of make, such as:
Comment #8
dmitrig01 commentedYeah, there's no way we can fix that without a lot of work ATM. Maybe in the future
Comment #9
pcambrasuscribe
Comment #10
dmitrig01 commentedComment #11
dmitrig01 commentedComment #12
pearcec commentedWhat needs to happen to make this work. Please explain and I will try to work up a solution. This is a complete show stopper.
Comment #13
dmitrig01 commentedThis is not a bug, this is a request for a feature (I had it set to a task as in, "this will get done eventually" as opposed to "here is my dream vision and I am requesting this as a feature"). This requires a major rewrite of the project aspect of drush make, separating the download functionality from the moving functionality: first, all the files need to be downloaded, then they need to be recursed through until recursion is complete, and then, only after, they need to be moved into place.
Comment #14
dmitrig01 commentedAnd, it's postponed because I'm working to try to get a stable 2.0 release out before biting off such an ambitious feature.
Comment #15
helmo commented[ Powered by #1115636: Issue Macros and Templates - Drush Make]
Drush make is being merged into drush core (discussed in issue:#1310130: Put drush make in drush core)
This means that the issue queue is also moving. The Drush project has a component called 'Make' for this purpose.
We would like to take this opportunity to leave behind old/obsolete issues, allowing us to focus on a stable make command in core. E.g. one of the major tasks ahead is making more use of the Drush core code for handling downloads and decompression.
If you feel that this issue is still relevant, feel free to re-open and move it to the Drush queue.
More information will be posted on the drush_make and drush project pages.
NOTE: I'm afraid this would add a lot of complexity, and require a lot of work as #13 mentions. The "simple" solution for #7 would in my opinion to move the patch line to the outer makefile. It's a matter of scoping.