5,705
edits
Changes
Jump to navigation
Jump to search
Line 11:
Line 11: + + + +
Talk:Sugar Network/Recipe Specification (view source)
Revision as of 09:39, 8 February 2011
, 09:39, 8 February 2011→Change Logs
: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)
=== Auxiliary Section ===
=== Auxiliary Section ===