[76968] trunk/dports/kde/skrooge/Portfile

Ryan Schmidt ryandesign at macports.org
Tue Mar 15 15:38:39 PDT 2011


On Mar 15, 2011, at 14:25, mk at macports.org wrote:

> Revision: 76968
>          http://trac.macports.org/changeset/76968
> Author:   mk at macports.org
> Date:     2011-03-15 12:25:12 -0700 (Tue, 15 Mar 2011)
> Log Message:
> -----------
> skrooge: introduce a kbuildsycoca4 call at post-activate phase to ensure that skrooge gets to run even if the KDE framework forgot to trigger this itself
> 
> Modified Paths:
> --------------
>    trunk/dports/kde/skrooge/Portfile
> 
> Modified: trunk/dports/kde/skrooge/Portfile
> ===================================================================
> --- trunk/dports/kde/skrooge/Portfile	2011-03-15 19:18:47 UTC (rev 76967)
> +++ trunk/dports/kde/skrooge/Portfile	2011-03-15 19:25:12 UTC (rev 76968)
> @@ -6,6 +6,7 @@
> 
> name                skrooge
> version             0.8.1
> +revision            1
> 
> categories          kde finance
> maintainers         mk pixilla openmaintainer
> @@ -38,3 +39,8 @@
>                     port:kdebase4-runtime \
>                     port:oxygen-icons
> 
> +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"
> +} 

We can probably dispense with that ui_msg. Does a user installing skrooge know what kbuildsycoca4 is, or care about it, and is there anything you want the user to do in response to this message? I suspect the answer to all these is "no."





More information about the macports-dev mailing list