On Fri, 2017-12-01 at 10:30 +0100, Peter Czanik wrote:
On 12/01/2017 09:06 AM, Dominique Leuenberger / DimStar wrote:
On Fri, 2017-12-01 at 09:01 +0100, Peter Czanik wrote:
For the public record (I mentioned the same on the submit request): Repo checker is right.
The packaging guidelines about 'merging packages' was not adhered to:
https://en.opensuse.org/openSUSE:Package_dependencies#Merging_a _pac kage
Once this is adhered to, r-c won't complain and let this package pass.
OK. So I should revoke this request.
Is it OK if I modify packages this way?
Provides: libevtlog0 = 0.2.13 Obsoletes: libevtlog0 <= 0.2.13
This one no: the right thing here is to also split libevtlog0 in the new souece package (syslog-ng), according to the shared library packaging policy. Then, as the name stays the same, no provides/obsoletes are needed
But why, if no other package is using it? (history: originally it was developed as a generic logging library for RFC 5424 syslog, but as actually syslog-ng was the only user for many years, it was merged)
There are header files and a public library - hence it has to adhere to the shared library packaging policy. The fact that nothing else uses it yet does not justify to ignore this specific packaging guideline. libevtlog.so.0 has to live in the libevtlog0 package (which you can generate from the syslog-ng sources, no problem with that) Cheers Dominique