Sverre Rabbelier venit, vidit, dixit 17.09.2010 23:07: > Heya, > > [+Jonathan again] > > On Fri, Sep 17, 2010 at 23:00, Michael J Gruber > <git@xxxxxxxxxxxxxxxxxxxx> wrote: >> The solution with setup.cfg avoids this and is cleaner anyways. > > This does feel a lot cleaner, I like this approach better than the v1 > one. I suspect Junio's question still stands though: > > On Fri, Sep 17, 2010 at 20:41, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> Hmm, wouldn't this interfere with the install target if you do not tell >> the "setup.py install" where your built stuff lives? > No, it addresses that also. Maybe my note after the boiler plate was not clear enough, but the "build" setting in setup.cfg also governs the build phase of "setup.py install". Install would work with v1 also but would possibly create another dir during the build phase, with v2 both build phases (that of the build subcommand as well as that of the install subcommand) use the same setting. Michael -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html