On Tuesday 07 February 2006 21:58, Nicolas François <[EMAIL PROTECTED]> wrote: > Do you think we need a versionned dependency on libselinux1-dev?
We don't have any plans to break the interface, but new things are periodically added to it. So it would make sense to have a versioned dependency on the current version to avoid any possible problems, as long as the SE Linux specific code in the applications doesn't change then the versioned dependency should not need to be changed. > Also, given the current build system, the tools of the login package > (login, su, lastlog, faillog, sg) will have a shared library dependency on > the selinux libraries. > Do you think that may be a problem? That will work, such a bug has been in other packages in the past and they have worked OK. It's a bad idea though and you don't want to do that. It's ideal if -lselinux is only passed as a compile option if there is actual SE Linux code compiled as part of the application and linked directly into it. Some programs get libselinux indirectly through linking against pam or other things, they should not be compiled with -lselinux either.