Current Makefile system is inconvenient/limited

Current Makefile system is inconvenient/limited

[Michael Seyfert]

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@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Current Makefile system is inconvenient/limited

[piruthiviraj natarajan]

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

I think the whole implementation of selinux is unachievable in Debian as
far as I have tested until the Wheezy RCs and Sid too.
You cannot set an enforcing mode in Debian and have a smooth working system
as RHEL clones or Fedora.
On Wed, May 1, 2013 at 5:44 PM, Michael Seyfert <michael@codesand.org>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@tycho.nsa.govwith
> the words "unsubscribe selinux" without quotes as the message.
>

[-- Attachment #2: Type: text/html, Size: 1259 bytes --]

Re: Current Makefile system is inconvenient/limited

[Joshua Brindle]

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@codesand.org> 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@tycho.nsa.gov 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@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Current Makefile system is inconvenient/limited

[Michael Seyfert]

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@codesand.org> 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@tycho.nsa.gov 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@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Current Makefile system is inconvenient/limited

[William Roberts]

[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]

Ive used scons, for my own my projects, but had to roll all the packaging
stuff on my own. Its really limited in that respect, but made the build
dirt simple.


On Wed, May 1, 2013 at 3:57 PM, Michael Seyfert <michael@codesand.org>wrote:

> 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@codesand.org>
> 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@tycho.nsa.gov 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@tycho.nsa.govwith
> the words "unsubscribe selinux" without quotes as the message.
>



-- 
Respectfully,

William C Roberts

[-- Attachment #2: Type: text/html, Size: 2479 bytes --]

Re: Current Makefile system is inconvenient/limited

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/01/2013 08:14 AM, Michael Seyfert 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?
> 
Patches Welcomed.

I don't think anyone loves it, but most people do not hate it enough to fix it...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlGH11UACgkQrlYvE4MpobPkHwCfXbAlk6WCJdhXqH0g4jaeCYp9
BSQAnij1i4qDFngpO0zhKxmbKt2X/MG5
=tYfk
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Current Makefile system is inconvenient/limited

[Michael Seyfert]

> On 05/01/2013 08:14 AM, Michael Seyfert 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?
> > 
> Patches Welcomed.
> 
> I don't think anyone loves it, but most people do not hate it enough to fix it...

I'm switching selinux (not tools yet) over to SCons for my personal use and to learn
more about the code. I suppose I could upload my (incomplete) patch for
you guys to look at if you want.

-- 
Michael Seyfert

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.