On 2017-10-16 12:56:24 +0000, Dominique Leuenberger / DimStar wrote:
On Mon, 2017-10-16 at 14:19 +0200, Peter Czanik wrote:
Hi,
On 10/16/2017 02:11 PM, Richard Brown wrote:
- Minimal acceptable - just mention upstream release and packaging changes - Ideal - upstream release, packaging changes and packagers "highlights" of release if the package maintainer is confident they have a meaningful understanding (I have more faith than you ;))
Depending on my time and mood I use one of these. Copy & paste of upstream changelog makes no sense especially knowing that not all upstream features can be packaged in openSUSE. For example in case of syslog-ng, JAR files necessary to build Java-based destinations are missing from openSUSE. So detailing Elasticsearch or Hadoop related changes makes no sense at all.
This is actually what the guideline says you should be doing when using upstream's changelog: strip irrelevant things (Windows installer fixes? MacOSX build fix, non-openSUSE releated feature fixes).
So you do it all right - keep on doing it :) - But I agree: doing serious packaging takes time and also some understanding (I keep on telling people: don't just copy/paste the NEWS, but actually READ/Understand it... not uncommonly you find out about new build deps you might want to check, or even obsolete ones)
TBH the *understand* part is the important bit. if you submit something it would be nice if you have at least some understand of the impact of your submission. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org