Bug#775277: should we split krb5-kpropd into a separate package?

2016-01-18 Thread Michael Weiser
Hi Sam, On Fri, Oct 16, 2015 at 01:24:05PM +, Sam Hartman wrote: > I'm sorry. > I thought I had responded long ago on this, but apparently not. > I think the package split makes sense. I finally got a chance to give this kpropd package split a whirl. Attached is my first take on a patch.

Bug#775277: should we split krb5-kpropd into a separate package?

2015-10-16 Thread Sam Hartman
I'm sorry. I thought I had responded long ago on this, but apparently not. I think the package split makes sense.

Bug#775277: should we split krb5-kpropd into a separate package?

2015-10-13 Thread Benjamin Kaduk
On Tue, 13 Oct 2015, Michael Weiser wrote: > Hi Ben, > > > Looking at the patch, it feels awkward to manually install the unit file > > and sysv script to the staging directory. If we created a new > > krb5-kpropd package to be installed only on slave KDCs, then we could > > benefit from the

Bug#775277: should we split krb5-kpropd into a separate package?

2015-10-13 Thread Michael Weiser
Hi Ben, > Looking at the patch, it feels awkward to manually install the unit file > and sysv script to the staging directory. If we created a new > krb5-kpropd package to be installed only on slave KDCs, then we could > benefit from the debian/packagename.init magic and also have the script >

Bug#775277: should we split krb5-kpropd into a separate package?

2015-06-25 Thread Benjamin Kaduk
Looking at the patch, it feels awkward to manually install the unit file and sysv script to the staging directory. If we created a new krb5-kpropd package to be installed only on slave KDCs, then we could benefit from the debian/packagename.init magic and also have the script be active by