10,505
edits
Changes
Jump to navigation
Jump to search
Line 11:
Line 11: + + + +
Talk:Sugar Network/Recipe Specification (view source)
Revision as of 09:13, 8 February 2011
, 09:13, 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)
=== Auxiliary Section ===
A while back, I tried to drum up interest in adding optional fields to activity.info that would enable the developer to communicate to the packager so that the packager would not have to hunt for information needed in creating an .rpm or .deb. Didn't get much traction at the time, but it seems we have an opportunity to exploit your proposal to this end. SDZ had helped me come up with a short list of things that would be trivial for developers to itemize... will try to recreate it. --[[User:Walter|Walter]] 08:13, 8 February 2011 (EST)