Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
base system
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
28 Jun 2012 at 17:38 UTC
Updated:
29 Jul 2014 at 20:51 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mr.baileysAgreed that it makes sense to have the composer.json file be valid (although this seems only required when publishing a package).
Tested the patch and confirms that the file is now valid.
My only doubt is whether "drupal/core" would be a better name than "drupal/drupal"?
Comment #2
robloachMy thinking was that it's http://drupal.org/project/drupal , and not http://drupal.org/project/core . Happy with either one though!
Comment #3
mr.baileysLet's go with
drupal/drupal. The name is not cast in stone as long as the package is not published, so if and when we decide to publish we can still discuss naming.For now, let's just make sure the composer.json file is valid.
Comment #4
webchickQuestion. Is it possible to be more specific on the license? As http://drupal.org/licensing/faq points out, our license is not "GPL 2.0" but rather "GPL version 2 or later."
Comment #5
mr.baileysAnswer. Yes, it is :)
GPL-2.0+ is a valid license notation for composer, see http://getcomposer.org/doc/04-schema.md#license
Updated patch attached.
Comment #6
robloachLet's do #1805316: Move composer.json to the project root too.
Comment #7
webchickCool, I'm sure that description could (and probably will ;)) be bikeshedded more but this resolves the immediate issue.
Committed and pushed to 8.x. Thanks!