Keep a copy of makefiles when creating platforms [#1372612]

If a platform is built according to best-practices, it will be based on a Drush makefile. While we keep a link to said makefile, it can be difficult to reconstruct a platform, as makefiles are likely to change over time. If we build it from a remote source, it could be lost altogether.

If we copied the makefile used to build a platform into the platform docroot itself, there would be a more permanent record, and would make cloning a platform easier and more reliable (ref.:#906936: Allow creation of a platform using an existing platform's information). Also, if we #1372614: Include platform makefile with site backups, it would make backups more portable, by allowing us to #1372622: Import sites from backups.

Comments

Comment #1

ergonlogic

he/him

English

Montréal, Québec 🇨🇦

commented 16 December 2011 at 06:17

Version:

6.x-1.x-dev

» 6.x-2.x-dev

Comment #2

gboudrias commented 22 December 2011 at 21:15

Some of us include other makefiles in their makefile. Therefore, we would have to keep copies of all the makefiles involved.

I'm not sure how much of an obstacle that is but I thought it was worth mentioning.

Comment #3

ergonlogic

he/him

English

Montréal, Québec 🇨🇦

commented 22 December 2011 at 21:30

It's possible this issue should move to the drush_make queue...

I think it would be preferable to keep one makefile that's compiled from the various includes, if any.

Comment #4

helmo commented 23 December 2011 at 14:42

That would be the Make component in the Drush queue these days...

There already is an issue the relates to this: #1212686: Create a versioned make file when running drush make with option --make-generate

The behaviour for, recursively, included makefiles has not really been discussed there. But the use-case there might be very compatible with the one from this issue.