By Risse


2019-02-08 07:18:39 8 Comments

I am getting some old and mixed documentation issues with building a release for a Drupal 8-based distribution Drupal.org.

The main documentation is How to package a distribution on Drupal.org, which says to use drush make to create a drupal-org.make file. However, when I try to run this command on my site, I get the following error message.

Make has been removed, in favor of Composer. Use the make-convert command in Drush 8 to quickly upgrade your build to Composer.

That's fine, since I am already using Composer for the project! But how do I actually then publish these dependencies on Drupal.org? Drupal.org is definitely not reading the composer.json file, and building the zip files.

Do I just have to manually make a git tag which includes all the files in the *vendoré directory, so that Drupal.org knows to build this?

I am running Drush version 9.5.2.

1 comments

@kiamlaluno 2019-02-08 08:53:55

On Drupal.org, there isn't yet support for a distibution composer.json file, as reported on Support for distributions.

The package system used from Drupal.org, to be able to build the package files for a distribution, requires just two files: drupal-org.make and drupal-org-core.make. The latter is only necessary when using a Drupal release that is not official.

If your system doesn't allow you to create a .make file as required from Drupal.org, you can manually create it with any text editor, as long as you use the correct file format (see Example drupal.org make file), and you follow what reported in Drupal.org distribution packaging requirements. In particular, see the notes reported at the beginning.

  • External libraries are validated against a whitelist of GPL-compatible libraries since all code distributed from Drupal.org must be GPL compatible
  • Git clones from Drupal.org sandboxes (as opposed to full projects) are not supported
  • Patches hosted on servers other than Drupal.org are not supported
  • Modules and themes hosted on servers other than Drupal.org are not supported
  • If you need to specify anything other than an official release of the Drupal core project itself, that needs to go into a separate drupal-org-core.make file
  • If you request a specific Git revision you must also define the branch that revision came from

In future, some of those restrictions could be lift. There are feature requests / bugs opened in the packages.drupal.org issue queue.

Related Questions

Sponsored Content

1 Answered Questions

2 Answered Questions

[SOLVED] Why is Drupal Core not updating via composer?

  • 2018-07-18 23:41:50
  • usernameabc
  • 1932 View
  • 2 Score
  • 2 Answer
  • Tags:   8 composer

1 Answered Questions

[SOLVED] How do I update core to 8.5?

  • 2018-03-31 18:45:55
  • user5950
  • 1044 View
  • 0 Score
  • 1 Answer
  • Tags:   8 updating composer

1 Answered Questions

[SOLVED] How do I update core with Composer?

  • 2016-06-16 19:52:15
  • DrupalMonster
  • 5502 View
  • 10 Score
  • 1 Answer
  • Tags:   8 composer

1 Answered Questions

[SOLVED] Managing module library dependencies with composer

1 Answered Questions

Information added by Drupal.org on Distribution

  • 2018-01-18 20:08:44
  • Dragu Alexandru
  • 57 View
  • 0 Score
  • 1 Answer
  • Tags:   distributions

1 Answered Questions

[SOLVED] How can I upgrade ONLY Drupal core with composer?

  • 2017-08-14 19:12:36
  • RaisinBranCrunch
  • 982 View
  • 4 Score
  • 1 Answer
  • Tags:   8 updating composer

1 Answered Questions

[SOLVED] How to add dependency to a custom module with drupal-composer?

  • 2016-04-15 11:12:25
  • user2637046
  • 1304 View
  • 2 Score
  • 1 Answer
  • Tags:   8 composer

1 Answered Questions

Installing a profile inherited from an existing distribution

2 Answered Questions

[SOLVED] How can I include Guzzle as a library in a distribution?

Sponsored Content