[apparmor] [PATCH] towards a common build infrastructure

[Christian Boltz]

Hello,

Am Samstag, 5. Mai 2012 schrieb Kees Cook:
> I'd like to start trying to move to a common autoconf infrastructure
> where the build elements are selected at configure time, etc. This
> will let us get rid of the unusual common/Make.rules logic, provide
> cleaner common build targets, potential for easier parallelization of
> the build, etc.

I prefer hand-written Makefiles - but that might be a matter of personal 
taste ;-) (and, in my case, missing knownledge about automake)

That said: Jeff maintained a patch to use automake everywhere up to 
AppArmor 2.6.x. When I took over maintenance of the AppArmor package, 
I dropped it in favor of the upstream build system. Even if I needed to 
add 10 make calls from the spec, I still found that easier than 
maintaining a 370 kB patch ;-)

Nevertheless it might be easier for you to update Jeff's patch (it 
doesn't apply to 2.7.x or trunk) than writing everything from scratch.

If you are interested, you can find it on
https://build.opensuse.org/package/files?package=apparmor_2_6&project=security%3Aapparmor
>From there, take the files
- apparmor-2.5.1-unified-build (the main patch, 370 kB)
- apparmor-2.5.1-rpmlint-asprintf (small additional patch, depends on 
  the first patch, not sure if it is still needed)

> === modified file 'README'

You only deleted the lines describing the current build "system", but 
didn't add any note how to build AppArmor with automake...

Another question - what is the target version for changing the build 
system? Do you want to include it in 2.8?


Regards,

Christian Boltz
-- 
[Re: Wie krieg ich meinen Ratti in mutt zurueck?]
In der procmail einfach angeben:
  formail -I From: ratti at gesindel.de (Ratti)
Dann sind _ALLE_ Mails von Ratti.
[Ratti (welcher denn? ;-) in suse-linux]