On Thu, 2011-09-15 at 04:44 +0200, Guido Trentalancia wrote: > > The above will break when building checkpolicy separately. > > Yes it will. But it also avoids linking an existing old static library > when building from the whole git bundle. You can already avoid that problem by building with make DESTDIR=~/out install (which will then install libsepol.a under ~/out/usr/lib and use it rather than the system one when linking subsequent libraries and programs), so our current build procedure isn't broken, just the newly proposed one. > Before creating each release of the separate components, that piece of > patch could be reverted or otherwise a script could invoke sed on the > affected Makefiles. I don't see that as a maintainable solution. What other upstream projects patch their Makefiles before release and thus ship a different set of Makefiles than the ones they are using themselves for testing? -- Stephen Smalley National Security Agency -- 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.
