From kde-release-team Wed Jul 27 22:03:08 2011 From: Nicolas Alvarez Date: Wed, 27 Jul 2011 22:03:08 +0000 To: kde-release-team Subject: Re: RFC: Release Management Going Forward Message-Id: X-MARC-Message: https://marc.info/?l=kde-release-team&m=131180423413723 Dirk Mueller wrote: > is there a way to tell it to not run make install after every module? for > packagers, the step of "make" and "make install" must be completely > seperate. No, that's fundamentally impossible. If an app and a library get split, the app's buildsystem will expect the library to be compiled *and installed* before the app is configured. To build them in a monolithic tarball again, there are two ways: configure lib, compile lib, install lib, configure app, compile app, install app (what superbuild does); or *modify* the app's buildsystem to (optionally?) work as it did before, grabbing the library from the build directory. The whole point of superbuild is letting you create a monolithic tarball without modifying anything from the individual components being built. -- Nicolas _______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team