On Sunday 10 May 2009, Eric Noulard wrote: > 2009/5/9 Alexander Neundorf <[email protected]>: > > On Thursday 07 May 2009, Eric Noulard wrote: > > ... > > > >> 1) Add more CPACK_RPM_XXX specific var such like: > >> CPACK_RPM_POST_INSTALL_SCRIPT_FILE > >> CPACK_RPM_POST_UNINSTALL_SCRIPT_FILE > >> > >> which may be used to specify the corresponding scripts > >> that will be embedded in the generated spec file. > > > > Just a thought, do you think this could in some way with the > > INSTALL(SCRIPT/CODE ... ) command ? > > I guess quite often this already does what is required (at least in KDE > > it also does the update-icon-cache etc. stuff). > > But a problem would be that then cmake would be necessary when installing > > such a RPM :-/ > > Yes I did think about that too just as you did. > In fact the notion of install-time script may be supported by various > CPack generator (DEB, RPM , NSIS etc...).
Yes. > It would be a good thing to either: > - launch INSTALL(SCRIPT/CODE ... ) with an extra cmake dependency > (the dependency may be added by the generator if it knows that > there exists some INSTALL(SCRIPT/CODE ... ) rules) > > - translate INSTALL(SCRIPT/CODE ... ) into it's own supported language. > For example RPM uses bash and I'm pretty sure CMake scripts may > be translated into shell scripts. > That would be nicer (no extra dependency) but surely harder to > implement. Yes. > > Another thing I did not look at is "WHEN" INSTALL(SCRIPT/CODE ... ) > are launched? > In RPM you can usually chose between pre-install scripts and > post-install scripts > (and their uninstall counterpart). > > Currently the INSTALL(SCRIPT/CODE ... ) script is too loose, moreover > as far as I know there aren't any "uninstall rules"... > > So currently I think we can get INSTALL(SCRIPT/CODE ... ) to be embedded > into RPM post-install rules, I do have to find where thoses scripts > are generated though. > > There will be several remaining issues: > 1) You usually don't want to run "INSTALL(SCRIPT/CODE ... )" when > building the RPM, however now since CPack basically do install with > relocation they are. Hmm, yes, usually, but maybe sometimes you do want to run them... > 2) There is no associated "uninstall" rules, which is just bad > because you may > leave dangling menu entry and/or icon. Hmm ? > 3) You ger an extra cmake dependency ... > > > Alex, > Does KDE uses INSTALL(SCRIPT/CODE ... ) ? Yes. > If yes how do packager do for handling that in DEB, RPM ... ? This is done completely independent. The official distribution packager build their packages themselves anyway. Alex _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
