Re: [Gimp-developer] gimp-plugin-template: install
Hi, Quoting Sven Neumann [EMAIL PROTECTED]: I don't think we should change this behaviour but we could very easily add another install target (for example called install-user) that installs the plug-in to the user's plug-in directory. This will only work for a small subset of plug-ins though. Most plug-ins handled by a gimp-plugin-template framework are complex plug-ins that install more than just a single plug-in. Usually there will be help files, translations, perhaps data files loaded at runtime. The extra installation target may make people think that the plug-in has been successfully installed with all its additional files while really only the exectuable has been installed. I am not convinved that it would be a good idea to do such a change. This brings up an interesting question... is it possible to install a plug-in in the user's directory, and have translations managed by gettext? Where do the .mo files get installed in this case, and how can one make gettext aware of them? Cheers, Dave. -- Dave Neary Lyon, France ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
Hi, Dave Neary [EMAIL PROTECTED] writes: This brings up an interesting question... is it possible to install a plug-in in the user's directory, and have translations managed by gettext? Where do the .mo files get installed in this case, and how can one make gettext aware of them? This is all already handled. Just have a look at gimp-plugin-template or gimp-freetype. You can install everything but the actual plug-in executable into whatever prefix you specify. Not a very interesting question... Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
Hi,
Joseph Heled [EMAIL PROTECTED] writes:
gimp-plugin-template is an example of an autoconf/automake packaged
plug-in that is to be installed system-wide. It doesn't handle
installation to the users plug-in directory. Why should it?
Because,
- On some system you don't have administrative rights (say the university)
- The gimp is set up to allow full plugins to be installed in ~..gimp-2.0
- 'gimptool --install' defaults to installing in ~/.gimp-2.0
The build environment as setup by gimp-plugin-template is a standard
autotools setup and it would ideally behave like any other such
package. Unfortunately this doesn't work perfectly for GIMP and we
override the install target to install to the GIMP plug-in directory
instead of to ${prefix}/bin.
I don't think we should change this behaviour but we could very easily
add another install target (for example called install-user) that
installs the plug-in to the user's plug-in directory. This will only
work for a small subset of plug-ins though. Most plug-ins handled by a
gimp-plugin-template framework are complex plug-ins that install more
than just a single plug-in. Usually there will be help files,
translations, perhaps data files loaded at runtime. The extra
installation target may make people think that the plug-in has been
successfully installed with all its additional files while really only
the exectuable has been installed. I am not convinved that it would be
a good idea to do such a change.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
Hi, Joseph Heled wrote: Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? gimp-plugin-template is an example of an autoconf/automake packaged plug-in that is to be installed system-wide. It doesn't handle installation to the users plug-in directory. Why should it? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
Sven Neumann wrote: Hi, Joseph Heled wrote: Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? gimp-plugin-template is an example of an autoconf/automake packaged plug-in that is to be installed system-wide. It doesn't handle installation to the users plug-in directory. Why should it? Because, - On some system you don't have administrative rights (say the university) - The gimp is set up to allow full plugins to be installed in ~..gimp-2.0 - 'gimptool --install' defaults to installing in ~/.gimp-2.0 -Joseph Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] gimp-plugin-template: install
Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? Thanks, Joseph ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] gimp-plugin-template: install
Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? Thanks, Joseph ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
On Friday 23 July 2004 09:04 am, Joseph Heled wrote: Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? You can type ./configure --help for a list of parameters that influence the installation. Maybe ./configure --prefix=/home/myname/gimp_plugins/ or similar does what you need (install where you have write-access to). Markus. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
Hi Joseph, Joseph Heled wrote: Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? configure --prefix=~/gimp-2.0 should work. But if you would like to install your plug-in in the GIMP user directory (in $HOME/.gimp-2.0/plug-ins), I don't know how to do that. Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] CV: http://dneary.free.fr/CV/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
David Neary wrote: Hi Joseph, Joseph Heled wrote: Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? configure --prefix=~/gimp-2.0 should work. But if you would like to install your plug-in in the GIMP user directory (in $HOME/.gimp-2.0/plug-ins), I don't know how to do that. which is exactly my problem. configure sets this from GIMP_LIBDIR=`$PKG_CONFIG --variable=gimplibdir gimp-2.0` And gives no way to override it. I think this is a configure mistake. -Joseph Cheers, Dave. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
