Greg Freemyer
On Tue, Mar 6, 2012 at 6:18 PM, Marguerite Su wrote:
On Wed, Mar 7, 2012 at 5:06 AM, Greg Freemyer
wrote: All,
I just updated perl-Image-Exiftool in my home project.
I dumped all the changes from the change log into our *.changes file, but its 200 lines of info for just the last 6 months.
Should I leave it that way, or replace it with a URL?
Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi, Greg,
1. I think *.changes is where your changes for spec file go to. there's a scriptlet "changes2spec" will write *.changes to %changelog section of spec file.
upstream changes should go to %files:
%files %defattr(-,root,root) %doc ChangeLog
where will be placed under /usr/share/doc/packages/%{name}/. it means you don't need to merge. ChangeLog is the changelog for developers, for the source code, *.changes is the changelog for packager, for the distributive binary packge itself.
2. all changes from upstream in source code can be summarized as one line in *.changes, which is:
------------------------------------------------------------------------------------------------- Tue Mar 6 23:11:33 UTC 2012 - i#marguerite.su
- update version 2.0 (or "initial package 1.0")
Marguerite,
In general, I believe if the changelog for a upgraded package is just a few lines long, we are encouraged to add it to the *.changes file.
In this case, the ChangeLog entry is only ~ 10 lines per release, but upstream is doing a new release roughly every 10 days!.
So there have been 12 upstream releases since I last updated the source code in Sept. 2011.
I think I'll try the summarization route with a url for details.
Note, the "Changes" file from upstream is already in the %doc section of %files for this package, so I'll mention that as well in the *.changes file.
Greg
Greg, A URL is just fine, I sometimes paste it to .changes, directing here or bugzilla. To keep .changes clean, you can use URL short service like is.gd As you said, every release is short, but in total it is huge, anyway it's huge, so should be cleaned. Mplayer has four or five line of changes, but its spec file doesn't include them at all. Because it's a long live package has 50% doc in spec file. If it's there, I think no need to especially mention it, because every packager knows where to find it, while end users couldn't see your spec file at all. Marguerite -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org