Closed stof closed 7 years ago
Nice, I didn't know about this. For those interested, here's the documentation:
https://getcomposer.org/doc/04-schema.md#type
This is not my project, so it may be not my place to ask, but could you squash the commits, please? Two of the three are nonfunctional.
This PR should be rejected if #21 is meant to be merged though, as it will then bring code.
However, I still think that using keywords rather than type to hold standard
is better according to the composer schema.
This and other future PDS publications are likely to include code of some sort, so "metapackage" seems inappropriate.
As for using keywords instead of the package type: noted, and pondering. :-)
@pmjones you can change the type of package once it starts having code in it.
As this package does not provide any code and is meant to be required as an indication of adoption, forcing all projects to download it does not make sense. Metapackages cover this case.