Mailinglist Archive: opensuse-packaging (235 mails)
| < Previous | Next > |
Re: [opensuse-packaging] 200 lines of changes?
- From: Marguerite Su <i@xxxxxxxxxxxxx>
- Date: Wed, 7 Mar 2012 07:18:32 +0800
- Message-id: <CAK0PdAnitfKSf17Ak2Qbkvvf55VFzMxyguNN-ukDteFi8jhqqg@mail.gmail.com>
On Wed, Mar 7, 2012 at 5:06 AM, Greg Freemyer <greg.freemyer@xxxxxxxxx> wrote:
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")
an exception is updating from scm(git/svn/hg). there you should add
explanation why you update like "Upstream API changed", or "fixed bug
#78708" instead of copy the whole diff between versions to your
*.changes.
3. across the build service, the only exception, which placed upstream
changelog into *.changes, is NVIDIA graphics card. but it's not open
source. its packager can write anything to their products.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
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?
https://build.opensuse.org/package/view_file?file=perl-Image-ExifTool.changes&package=perl-Image-ExifTool&project=home%3Agregfreemyer%3ATools-for-forensic-boot-cd&rev=2e1a32ff0ebfbf51a109c50ef48bfd3a
Thanks
Greg
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
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")
an exception is updating from scm(git/svn/hg). there you should add
explanation why you update like "Upstream API changed", or "fixed bug
#78708" instead of copy the whole diff between versions to your
*.changes.
3. across the build service, the only exception, which placed upstream
changelog into *.changes, is NVIDIA graphics card. but it's not open
source. its packager can write anything to their products.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
| < Previous | Next > |