rlang Sun, 24 Nov 2019 09:52:18 +0000
Modified page: https://wiki.horde.org/Doc/Dev/HordeYmlFormat
New Revision: 5
Change log: Added code examples
@@ -7,9 +7,9 @@
Document .horde.yml format and how it relates to composer json and pear xml
TODO: beautify
-++ Meta data head
++++ Meta data head
id: string, mandatory, uppercase and minus Horde_ for libs,
lowercase for apps (horde, turba, Autoloader, Exception)
name: string, mandatory, Uppercase (Horde, Turba, Autoloader, Exception)
full: string, mandatory, a one-line description
@@ -64,11 +64,13 @@
identifier: BSD-2-Clause
uri: http://www.horde.org/licenses/bsd
</code>
-++ PHP and Pear Dependencies
++++ PHP and Pear Dependencies
-This covers PHP itself, php binary modules and PEAR dependencies both
inside horde and external
+This covers PHP itself, php binary modules and PEAR dependencies both
inside horde and external.
+For composer, pear dependencies on parts of horde get translated.
External dependencies get included as pear unless they are defined in
a conversion list in the components tool's config.
+See below for composer-only dependencies.
dependencies: top level structure for several optional keys
dependencies: required: multilevel list of mandatory dependencies
(php, pear, ext) - The key and all sub keys are optional
dependencies: required: php: optional key. The value should be a
version constraint string
--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: commits-unsubscr...@lists.horde.org
