Difference between revisions of "Talk:Sugar Network/Recipe Specification"
| 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) | ||
| + | |||
| + | === 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) | ||
Revision as of 08:13, 8 February 2011
Change Logs
Not sure that dates are so important as all the changes are tracked in git anyway. Version number would be important, however. But how does this differ from the info nominally kept in NEWS? Would we still need the NEWS file? --Walter 22:46, 7 February 2011 (EST)
For dates, yeah. In any case, people might use additional keys if they prefer. Might be NEWS as well, though some people (like me) will prefer "self contained" spec files (ie w/o NEWS). So, I guess having assumption that change log can be either in NEWS or in spec file, should be fine. Another reason to have changelog in spec (or in ini file format, ie not like arbitrary NEWS), is that it will be possible to use regular notation for translated strings, eg:
[v1] changelog = en-text changelog[ru] = ru-text
alsroot 22:57, 7 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"? --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. --Walter 08:13, 8 February 2011 (EST)