Talk:Sugar Network/Recipe Specification: Difference between revisions
m Alsroot moved page Talk:Platform Team/Recipe Specification to Talk:Sugar Network/Recipe Specification |
|||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
:I am fine with using a spec file instead of NEWS, but I am loathe to add yet another place where I track my changes (git commit messages, ASLO release notes, activity page in the wiki, NEWS, and now the spec file). Maybe we either phase out the NEWS file and/or automatically add its updates to the spec file when running "setup.py fix_manifest"? --[[User:Walter|Walter]] 08:08, 8 February 2011 (EST) | :I am fine with using a spec file instead of NEWS, but I am loathe to add yet another place where I track my changes (git commit messages, ASLO release notes, activity page in the wiki, NEWS, and now the spec file). Maybe we either phase out the NEWS file and/or automatically add its updates to the spec file when running "setup.py fix_manifest"? --[[User:Walter|Walter]] 08:08, 8 February 2011 (EST) | ||
::No questions that having the same data only in one place is a good point. Recipe spec is inspired by the same idea, i.e.: the same spec is activity.info to run activity; the same spec has instruction how to build your activity locally; the same spec has all info to build native packages directly (avoiding intermediate "repackaging") from activity. [[User:Alsroot|alsroot]] | |||
:: I was not thinking about having NEWS if recipe already contains changelog, though, as silbe said, might useful to reuse [http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog debian/changelog] files, but in this case would be useful to generate this file (thus do not mess with recipe) from {{Code|--message}} command line argument of {{Code|setup.py}} or {{Code|sweets}}. [[User:Alsroot|alsroot]] 08:39, 8 February 2011 (EST) | |||
:So, looks like there are more +1 for having {{Code|NEWS}} file instead of having it in recipe file. [[User:Alsroot|alsroot]] 21:18, 13 February 2011 (EST) | |||
=== Auxiliary Section === | === Auxiliary Section === | ||
| Line 19: | Line 25: | ||
:+1 --[[User:Walter|Walter]] 08:36, 8 February 2011 (EST) | :+1 --[[User:Walter|Walter]] 08:36, 8 February 2011 (EST) | ||
=== Where does this file live? === | |||
I gather from the examples that it lives in the top-level directory? Are we eliminating activity.info? --[[User:Walter|Walter]] 20:38, 13 February 2011 (EST) | |||
:I'm personally for continue using it, don't see any need in changing the rule. The top level {{Code|sweets.recipe}} is for non-activity projects (libraries and applications like {{Code|sugar}}). [[User:Alsroot|alsroot]] 21:13, 13 February 2011 (EST) | |||
::Hmm. The Python activity example points to the activity icon in activity/ which is a different syntax than we currently use. Maybe activity.info can be a symlink to the sweets.recipe? --[[User:Walter|Walter]] 22:24, 13 February 2011 (EST) | |||
::The icon path has changed since last I looked (or I was mistaken). --[[User:Walter|Walter]] 22:28, 13 February 2011 (EST) | |||
:::I've tuned spec. In any case, it should support backwards compatibility. [[User:Alsroot|alsroot]] 22:40, 13 February 2011 (EST) | |||