[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnash-dev] install vs install-plugins && klash
From: |
strk |
Subject: |
Re: [Gnash-dev] install vs install-plugins && klash |
Date: |
Sun, 18 May 2008 18:48:47 +0200 |
On Sun, May 18, 2008 at 06:16:53PM +0200, Rob Savoye wrote:
> strk wrote:
>
> >Yes, for the short term.
> >For the long term, since I don't agree on the default install dir,
> >I'd require a specific ./configure switch to enable install of the plugins
> >(ie: no default, only installed if you pick an install among
> >prefix|system|user)
>
> If you research how other KDE applications install their files, the
> current way, installing in $HOME/.kde *is* the correct way for end users
> trying to get a working Kparts plugin.
kdeaddons-3.5.9 installs by default in kde system dir, but accepts to install
all in --prefix if given (warning if it thinks it won't work):
----8<---- configure.in -------8<-------------
# Check if KDE_SET_PREFIX was called, and --prefix was passed to configure
if test -n "$kde_libs_prefix" -a -n "$given_prefix"; then
# And if so, warn when they don't match
if test "$kde_libs_prefix" != "$given_prefix"; then
# And if kde doesn't know about the prefix yet
echo ":"`kde-config --path exe`":" | grep ":$given_prefix/bin/:" 2>&1
>/dev/null
if test $? -ne 0; then
echo ""
echo "Warning: you chose to install this package in $given_prefix,"
echo "but KDE was found in $kde_libs_prefix."
echo "For this to work, you will need to tell KDE about the new
prefix, by ensuring"
echo "that KDEDIRS contains it, e.g. export
KDEDIRS=$given_prefix:$kde_libs_prefix"
echo "Then restart KDE."
echo ""
fi
fi
fi
----8<---- ./configure --help -------------8<-------------
By default, `make install' will install all the files in
`the kde prefix/bin', `the kde prefix/lib' etc. You can specify
an installation prefix other than `the kde prefix' using `--prefix',
for instance `--prefix=$HOME'.
> The only person that would want
> to install in the system directories is root. To do this now does
> require multiple configure options to Gnash, so having a single option
> to override the default to make this easier for package maintainers
> (--enable-kparts-system) is fine.
Yes, I'm suggesting a single option, for both plugins:
--with-plugins-install=system|user|prefix
> Installing the plugins in $prefix is completely wrong, as neither the
> NPPAI nor the KParts style plugins will actually load that way. We could
> install the plugins parts in $prefix, but we'd still be stuck making
> symbolic links to either $HOME/.kde or system directories to make the
> plugins actually work.
I'd just assume if a user intentionally calls --with-plugins-install=prefix
he knows what he's doing. We should make life easy for those that know what
they are doing...
--strk;
- [Gnash-dev] install vs install-plugins && klash, Russ Nelson, 2008/05/17
- Re: [Gnash-dev] install vs install-plugins && klash, Rob Savoye, 2008/05/18
- Re: [Gnash-dev] install vs install-plugins && klash, strk, 2008/05/18
- Re: [Gnash-dev] install vs install-plugins && klash, Rob Savoye, 2008/05/18
- Re: [Gnash-dev] install vs install-plugins && klash, strk, 2008/05/18
- Re: [Gnash-dev] install vs install-plugins && klash, Rob Savoye, 2008/05/18
- Re: [Gnash-dev] install vs install-plugins && klash, strk, 2008/05/18
- Re: [Gnash-dev] install vs install-plugins && klash, Rob Savoye, 2008/05/18
- Re: [Gnash-dev] install vs install-plugins && klash,
strk <=
- Re: [Gnash-dev] install vs install-plugins && klash, Rob Savoye, 2008/05/18