On Oct 4, 2012, at 5:31 PM, Bradley Giesbrecht wrote: > Maybe I missed something, what problem are we trying to solve?
You didn't miss it, I was just asking more in general. :-) Please see this thread for info about what's needed for KDE ports: > From: Marko Käning <[email protected]> > Date: March 15, 2011 8:19:01 PM GMT+01:00 > To: Developer-MacPorts Mailing-List <[email protected]> > Subject: Re: How to introduce a call to kbuildsycoca4 in a kde port > >> Depending on what it actually does this might be better to have once the >> program is installed in the proper place with post-activate {...}, like >> texhash. > Yep, thanks for that remark, you are absolutely right, only after activation > it has to be run: > This > --- > post-activate { > ui_msg "Calling kbuildsycoca4 in case KDE hasn't called it yet to make > sure that skrooge can run." > system "${prefix}/bin/kbuildsycoca4" > } > --- > is the way to go. > > Well, I don't need to change into any dir before executing the command. > > According to skrooge's developer the command is normally called by the KDE > framework, but in some cases, like here, it obviously isn't, which is why I > wanted to introduce this call as a precaution measure. > > Thanks a lot. > _______________________________________________ > macports-dev mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev OMG, only now I see that's 1.5 years ago already… But well, there was another thread just a few weeks ago where we went through this again. Greets, Marko _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
