polkit-1 for elogind

Andreas Messer andi at bastelmap.de
Thu Nov 22 18:05:51 GMT 2018

On Thu, Nov 22, 2018 at 09:36:36AM +0000, Mark Hindley wrote:
> On Wed, Nov 21, 2018 at 09:32:08PM +0000, Ian Jackson wrote:
> > I therefore conclude that the right approach is indeed that proposed
> > by Mark Hindley:
> > 
> > We should, in Debian, configure and build the whole policykit upstream
> > source code twice: once against libsystemd and once against
> > libelogind.
> I want to point out again that what I have done is based on what Svante and
> others did for Devuan.
> I have done some more work on cleaning up the builds and packaging dependencies.
> One question: how do we want to name the elogind flavour packages? Svante, I
> notice that in Devuan you changed from libfoo-1-elogind to libfoo-elogind-1. Can
> you remember why?

I think debian policy requires that package name ends with the .so library
major version number.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/attachments/20181122/495596dd/attachment.sig>

More information about the Debian-init-diversity mailing list