* Richard Guenther <rguenther(a)suse.de> [Jan 30. 2009 07:57]:
noticed that a lot of packages going in to Factory does not have
"proper" Changelog entries as explained to me (ie, copy redundant
information from NEWS/Changelog entries upstream and put it in
My question is, do we have a project wide policy for this, or would it
be enough to add what has been done by the package updater (ie, update
to version x.y.z, add/remove patch etc)?
Personally, I am in favor of not having to put it what changed upstream,
since in most cases, this would be contained in a NEWS/Changelog file
Well, there have been requests and (internal?) policy that an entry
* New upstream version 1.2.3
is not appropriate and that we indeed _should_ paste in (IMHO
redundant and not appropriate for the rmp .changes) contents from
So - we are just doing what is requested.
Yes, I think that the rpm .changes is to document _packaging_ changes
and not package changes.
Back when I was in-house I advocated to copy Changes, NEWS, whereever
the changelog for the software itself is, and I still do. It's very
convienient to be able to access this information when off-line, etc.
For sheer convienience it's great.
Besides. It's the changes to the software, hence the package. If you
dont want it, it should be called package-container changes.
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org