SCons or CMake maybe. I might try a few changes to make packaging for distributions easier. Thing is setools depends on parts of selinux and selinux depends on parts of setools, as you were saying. On Wed, May 01, 2013 at 08:43:30AM -0400, Joshua Brindle wrote: > No, we all think it. It's become unwieldy with optional dependencies > too. There are also mutual dependencies between parts of the SELinux > userspace. > > Do you have any suggestions on improving it? IMHO autoconf is hell on > earth, and it was attempted a couple time. Something like Scons > *might* help, but I'm not convinced. > > On Wed, May 1, 2013 at 8:14 AM, Michael Seyfert <michael@xxxxxxxxxxxx> wrote: > > The current system for building selinux requires a lot of workarounds like C_INCLUDE_PATH and is also interdependent on setools. I was looking at the debian packages and they require two build throughs of selinux just to get things to compile properly. Am I the only one that thinks this is a problem? > > -- > > Michael Seyfert > > > > -- > > This message was distributed to subscribers of the selinux mailing list. > > If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with > > the words "unsubscribe selinux" without quotes as the message. -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
