gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] gnash configure.ac ChangeLog macros/kde.m4


From: strk
Subject: Re: [Gnash-commit] gnash configure.ac ChangeLog macros/kde.m4
Date: Sat, 15 Mar 2008 16:24:32 +0100

On Sat, Mar 15, 2008 at 09:16:26AM -0600, Rob Savoye wrote:
> strk wrote:
> 
> > As someone pointed out, you may want to use symlinks to the actual
> > "enabling" of plugins.
> > It's nice to have --prefix respected always.
> 
>   But in this case if prefix is respected, then the plugin install won't
> work. We could write the actual files in /usr/local/lib/gnash or
> something like that, and symbolically link to the actual locations in
> the users $HOME/.kde, but what's the point ? Only the Java plugin
> requires a symbolic link, as it has to find ones entire java
> installation. Everything else gets copied.
> 
>   So I think the current behavior is finally the correct one, as klash
> installs correctly in $HOME/.kde, and works just fine that way. So since
> there is no more permission problems by default, I think we should just
> have install invoke install-plugins so we don't have to document or
> remember that plugin installation is a separate step. It works great now.

Installing in $HOME/.kde is NOT the correct behaviour.
Consider 'make distcheck'.
It would wipe out any good plugin you have in $HOME/.kde
while you're just testing.
That's the point of --prefix.

--strk;




reply via email to

[Prev in Thread] Current Thread [Next in Thread]