From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from goalie.tycho.ncsc.mil (goalie [144.51.3.250]) by tarius.tycho.ncsc.mil (8.13.1/8.13.1) with ESMTP id p89LkZ3Z006407 for ; Fri, 9 Sep 2011 17:46:35 -0400 Received: from cp-out8.libero.it (localhost [127.0.0.1]) by msux-gh1-uea02.nsa.gov (8.12.10/8.12.10) with ESMTP id p89LkYvK013614 for ; Fri, 9 Sep 2011 21:46:34 GMT Subject: Re: [RFC] Userspace top-level Makefile (was Re: [PATCH] Fix LIBDIR usage for load_policy) From: Guido Trentalancia To: Joshua Brindle Cc: Eric Paris , SELinux Mail List Date: Fri, 09 Sep 2011 23:46:29 +0200 In-Reply-To: <4E6A8707.9080602@manicmethod.com> References: <1315587716.2170.16.camel@vortex> <1315588656.2170.26.camel@vortex> <1315590383.2170.32.camel@vortex> <1315591143.2170.36.camel@vortex> <1315603187.2482.22.camel@vortex> <4E6A8707.9080602@manicmethod.com> Content-Type: text/plain; charset="UTF-8" Message-ID: <1315604790.2482.26.camel@vortex> Mime-Version: 1.0 Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov On Fri, 2011-09-09 at 17:37 -0400, Joshua Brindle wrote: > Guido Trentalancia wrote: > > -all install relabel clean test indent: > > +all relabel test indent: > > @for subdir in $(SUBDIRS); do \ > > - (cd $$subdir&& $(MAKE) $@) || exit 1; \ > > + (cd $$subdir&& $(MAKE) $@&& $(MAKE) install) || exit 1; \ > > + done > > + @for subdir_bin in $(SUBDIRS_BIN); do \ > > + (cd $$subdir_bin&& $(MAKE) $@) || exit 1; \ > > + done > > + > > +install: > > + @for subdir in $(SUBDIRS); do \ > > + (cd $$subdir&& $(MAKE) install) || exit 1; \ > > + done > > + @for subdir_bin in $(SUBDIRS_BIN); do \ > > + (cd $$subdir_bin&& $(MAKE) install) || exit 1; \ > > done > > > > install-pywrap swigify: > > @@ -17,6 +29,14 @@ install-pywrap swigify: > > (cd $$subdir&& $(MAKE) $@) || exit 1; \ > > done > > > > Nack. We can't require install in the build target and bail if it fails, this is > completely unfriendly to developers who don't want to install all the libraries > on their system during development, and those are the people using git. > > If you are doing work on libselinux and you install it to your system before > testing it locally you can easily break your machine and have to boot from a > rescue disk. Yes, sure, 100% agreed. It was clearly stated how dirty that was... It's just good for a laugh ;-) At the end, you can't really install anything without the user knowing (and explicitly requiring) that. But something like the other two solutions would probably be nice... Regards, Guido -- 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.