[Pkg-giraffe-discuss] How to proceed for d-push/z-push packaging?

[Carsten Schoenert]

Hi,

On 05.11.2016 10:19, Carsten Schoenert wrote:
[...]
> So how to go further?
> I would suggest to get in a state there Debian is providing the same
> packages as Kopano/Z-Push is providing now.
> Than there additional changes are needed to create a upgrade way for
> existing installations. And on top of that I would meld down the package
> list to a smaller count and handle a upgrade of existing Z-Push
> installations provided by packages from upstream. But that's maybe to
> much and needs to get targeted into Stretch+1. But this only under the
> condition if upstream is thinking the same.
> 
> I other people interested I would upload my WIP to GitHub or email the
> git patches here.

I prepared a first shoot.

https://github.com/tijuca/z-push-packaging

I reworked all existing packages and added most of the new ones except

 z-push-autodiscover
 z-push-config-apache
 z-push-config-apache-autodiscover

as it seems to me this packages could be meld together obviously. But
it's up to the person/people who maintain this. I also added
transitional packages for the old existing d-push packages.

There are more other really small packages that should not go into the
archive this way. I can image to collect them in z-push-backends,
z-push-tools z-push-kopano. This needs further discussion.

I haven't tested the current output. And also there seems to be more
work needed depended on the current php7 transition in testing, Stretch
will probably only shipping php7 packages. We will see.
As possible I was taking down Lintian warnings and errors. Some Lintian
output was resulting in overrides related to modified PEAR files in the
source.

If anyone want to take over further development for d-push/z-push feel
free to take what ever you want and do rebasing, modifying and
improving. I want have much time in the upcoming weeks for more work.

-- 
Regards
Carsten Schoenert