On Sun, Nov 05, 2017 at 07:54:52PM +0100, Uwe Kleine-König wrote: > Hello Josh, > > On 11/05/2017 06:44 PM, Josh Triplett wrote: > > On Sun, Nov 05, 2017 at 05:25:09PM +0100, Luc Van Oostenryck wrote: > >> From: Uwe Kleine-König <uwe@xxxxxxxxxxxxxxxxx> > >> > >> This way I can just use > >> > >> env PREFIX=/usr make install > >> > >> on the command line to install sparse into the system. > > > > You can already use "make PREFIX=/usr install" to do this, which seems > > far more conventional, and seems less error-prone (e.g. it won't pick up > > something random from the environment, only something intentionally put > > on the command line). > > Having PREFIX in the build environment and then being surprised that > it's picked up by a build isn't something I'd show consideration for. I could *imagine* it happening by way of using that variable as an intermediate step in, say, .bashrc, and not unsetting it; I don't know offhand of any other package that would be affected by it, since most use things like autotools and cmake that would not pick it up by the environment. I'm not saying that this is common, just that picking something up from the environment seems marginally more error-prone. -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
