Sugar Network/Recipe Specification: Difference between revisions

Line 22:

'''sweet''' = <name>

~~A short name~~ of the package. Only lower alphabetic, numeric, "+" or "-" symbols are allowed. Sweet value should be at least two characters long and start with an alphanumeric character.

An identifier of the package. Only lower alphabetic, numeric, "+" or "-" symbols are allowed. Sweet value should be at least two characters long and start with an alphanumeric character.

''sweet'' is used in several cases:

* OBS package name should be equal to ''sweet'' value,

* in 0isntall feed url - <code><nowiki>http</nowiki>://sweets.sugarlabs.org/''sweet''</code>,

* in native package names generated from ~~this~~ recipe ~~- <code>sweets-''sweet''</code>~~.

* in native package names generated from the recipe.

''~~'origin'~~'' ~~= <colon-separated-obs-project-path>[/<origin-sweet>]~~

Important note, ''sweet'' is not intended to be unique. That means that there are might be several implementations for the same ''sweet'' in the field. It could be different versions of the package from the same developper or even separate implementations from another developers.

~~If current package~~ is ~~a different implementation of another one, ''origin'' should point~~ to ~~original OBS project~~. ~~Also if current~~ ''sweet'' is different~~, original should be mentioned~~.

'''name''' = <package-name>

@@ Line 22: / Line 22: @@
   '''sweet''' = <name>
-A short name of the package. Only lower alphabetic, numeric, "+"  or "-" symbols are allowed. Sweet value should be at least two characters long and start with an alphanumeric character.
+An identifier of the package. Only lower alphabetic, numeric, "+"  or "-" symbols are allowed. Sweet value should be at least two characters long and start with an alphanumeric character.
 ''sweet'' is used in several cases:
-* OBS package name should be equal to ''sweet'' value,
 * in 0isntall feed url - <code><nowiki>http</nowiki>://sweets.sugarlabs.org/''sweet''</code>,
-* in native package names generated from this recipe - <code>sweets-''sweet''</code>.
+* in native package names generated from the recipe.
- '''origin''' = <colon-separated-obs-project-path>[/<origin-sweet>]
+Important note, ''sweet'' is not intended to be unique. That means that there are might be several implementations for the same ''sweet'' in the field. It could be different versions of the package from the same developper or even separate implementations from another developers.
-If current package is a different implementation of another one, ''origin'' should point to original OBS project. Also if current ''sweet'' is different, original should be mentioned.
   '''name''' = <package-name>