Re: gimptool using --prefix for install?
On Tue, Aug 01, 2000 at 10:59:50PM +0200, Alexander Skwar wrote:
Hello!
I'm using gimp 1.1.24. I'd like to write a RPM spec file for a plugin. In
RPM it is very much desirable to have the install not go to the "real"
directory, but to prefix the install dir with some other dir.
Can I somehow use gimptool to do this? I thought about something like
"gimptool --prefix ~/tmp/prefix-dir --install-admin-bin pluginfile", and
If you use the auto*stuff provided by the gimp-plugin-template module,
this should Just Work so long as you set the prefix to ~/tmp/prefix-dir/
before building the plug-in. The autostuff works by using gimptool to
find out the paths, but not to do the actual copying.
So, how can I find out where the plug-ins directory of gimp is?
To express the plug-in directory in terms of the prefix variable, the
configure script has this lovely little tidbit:
GIMP_PLUGIN_DIR=`gimptool --gimpplugindir | sed -e "s/$( gimptool --prefix | sed
's/\//\\//g')/\$\{prefix\}/"`
If you do get a spec file working with gimp-plugin-template, we'd
welcome its addition to the template for others to use.
--
Kevin Turner [EMAIL PROTECTED] | OpenPGP encryption welcome here
Plug-ins: They make GIMP do stuff. http://gimp-plug-ins.sourceforge.net/
This list is archived at http://marc.theaimsgroup.com/?l=gimp-developer
To unsubscribe, mail [EMAIL PROTECTED]
Re: gimptool using --prefix for install?
On Wed, Aug 02, 2000 at 01:26:00AM +0200, "\"Jürgen A. Erhard\"" [EMAIL PROTECTED] wrote: automake-using apps per default, usually) can do it. It's just Perl that doesn't seem to be able to honor that (according to older posts from you Marc), which is a shame (for Perl). Perl can do it very well. Have you read my posts? Or README.perl, which explains that it's PREFIX not --prefix? What perl cannot do is automagically find installed modules in that way, and that is only natural. The shame is really underinformed people (like you) who keep talking about things they lack essential information on :( I also don't know why perl is the primary target, most probably because its used much more often than python, which has the same problems, just like any other extension which uses an independently installed interpreter. basis... (and I hope that the rumored complete Perl rewrite will be helping here). It's impossible. How could gimp find plug-ins that are installed in /some/where/else unless you tell it? -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: gimptool using --prefix for install?
On Wed, Aug 02, 2000 at 12:08:18AM +0200, Alexander Skwar [EMAIL PROTECTED] wrote: ? Did I miss something? Why is it such a bad thing that programs should be installable in a user specified place? And why is RPM broken because of What you miss is that it's not "installing in a user-specified place" but "installing it in /usr/bin" but physically copying files somewhere else, which only rpm needs. You choose the installation location while configuring the program. wouldn't be a problem. But that is *BAD* as far as creating the rpm file is concerned. At least under linux, you don't need such fragile solutions (any ELF system provides better measures). You could also use chroot to work on any unix, although that would be difficult. ;) Ah! :-) Sure! -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: gimptool using --prefix for install?
Date: Tue, 1 Aug 2000 23:56:55 +0100 (BST) From: Austin Donnelly [EMAIL PROTECTED] Some work needs to be done on gimptool before 1.2 can release. In particular, we need to be able to use it to automate the building of DLL modules without using a gimp build tree. As long as we're on this subject, it would be very handy for there to be a way to install (and deinstall) auxiliary files. We (gimp-print) don't have any as of yet, but that's largely because we have no handy way of installing them. In the future (not in 3.2, which is what we hope to release in a few months), we'll probably want to ship printer definitions, color profiles, possibly dither matrices, and such as separate files rather than compiled in to the binary. -- Robert Krawitz [EMAIL PROTECTED] http://www.tiac.net/users/rlk/ Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for The Gimp Print -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton
Re: gimptool using --prefix for install?
On Wed, Aug 02, 2000 at 07:56:35AM -0400, Robert L Krawitz [EMAIL PROTECTED] wrote: be a way to install (and deinstall) auxiliary files. We (gimp-print) don't have any as of yet, but that's largely because we have no handy way of installing them. What support are you missing? I'd think that every plug-in should know best how to manage it's library space, and gimptool provides a lot of information, e.g. where to put architecture dependnet and/or independent library files, The only thing that I miss (from a cursory look) would be the user-dependent gimp directory. hope to release in a few months), we'll probably want to ship printer definitions, color profiles, possibly dither matrices, and such as separate files rather than compiled in to the binary. I think it's not a good idea to put knowledge about printer files (or any plug-in-specific data) into gimptool. What's wrong about just using $gimpdatadir/gimp-print? -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: gimptool using --prefix for install?
Date: Wed, 2 Aug 2000 14:43:30 +0200 From: Marc Lehmann [EMAIL PROTECTED] On Wed, Aug 02, 2000 at 07:56:35AM -0400, Robert L Krawitz [EMAIL PROTECTED] wrote: hope to release in a few months), we'll probably want to ship printer definitions, color profiles, possibly dither matrices, and such as separate files rather than compiled in to the binary. I think it's not a good idea to put knowledge about printer files (or any plug-in-specific data) into gimptool. What's wrong about just using $gimpdatadir/gimp-print? I don't think that gimptool should know anything about specific plugins. At the very least I want agreement on conventions about what goes where. -- Robert Krawitz [EMAIL PROTECTED] http://www.tiac.net/users/rlk/ Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for The Gimp Print -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton
gimptool using --prefix for install?
Hello! I'm using gimp 1.1.24. I'd like to write a RPM spec file for a plugin. In RPM it is very much desirable to have the install not go to the "real" directory, but to prefix the install dir with some other dir. Can I somehow use gimptool to do this? I thought about something like "gimptool --prefix ~/tmp/prefix-dir --install-admin-bin pluginfile", and then gimptool should install "pluginfile" to "``~/tmp/prefix-dir''/usr/lib/gimp/1.1/plug-ins/", (without all those ",' `) but this obviously does not work. So, how can I find out where the plug-ins directory of gimp is? Alexander Skwar -- Homepage: http://www.digitalprojects.com Sichere Mail? Mail an [EMAIL PROTECTED] fuer GnuPG Keys ICQ:7328191
Re: gimptool using --prefix for install?
On Tue, Aug 01, 2000 at 10:59:50PM +0200, Alexander Skwar [EMAIL PROTECTED] wrote: RPM it is very much desirable to have the install not go to the "real" directory, but to prefix the install dir with some other dir. rant again Why is that every program has to be "fixed" to be usable with rpm, and everbody even agrees with that, instead of just fixing rpm??? / ;) -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: gimptool using --prefix for install?
On Tue, Aug 01, 2000 at 11:31:42PM +0200, Marc Lehmann wrote: rant again Why is that every program has to be "fixed" to be usable with rpm, and everbody even agrees with that, instead of just fixing rpm??? / ? Did I miss something? Why is it such a bad thing that programs should be installable in a user specified place? And why is RPM broken because of that? If I were to write a SPEC file that only root could execute because during the install files get written to the "real" directories, that wouldn't be a problem. But that is *BAD* as far as creating the rpm file is concerned. ;) Ah! :-) Alexander Skwar -- Homepage: http://www.digitalprojects.com Sichere Mail? Mail an [EMAIL PROTECTED] fuer GnuPG Keys ICQ:7328191
Re: gimptool using --prefix for install?
"Marc" == Marc Lehmann [EMAIL PROTECTED] writes:
Marc On Tue, Aug 01, 2000 at 10:59:50PM +0200, Alexander Skwar
[EMAIL PROTECTED] wrote:
RPM it is very much desirable to have the install not go to the "real"
directory, but to prefix the install dir with some other dir.
Marc rant again
Marc Why is that every program has to be "fixed" to be usable
Marc with rpm, and everbody even agrees with that, instead of
Marc just fixing rpm???
Marc /
It's not just rpm. Lots of people want to install to some place
different from what the configure --prefix was. People using stow,
for example. Or package builders... dpkg does the same ("the same
sane"?)
And it's definitely not "every program". Tons of stuff (like all
automake-using apps per default, usually) can do it. It's just Perl
that doesn't seem to be able to honor that (according to older posts
from you Marc), which is a shame (for Perl).
I'm just happy that I don't have to fight this monster on a daily
basis... (and I hope that the rumored complete Perl rewrite will be
helping here).
Bye, J
--
Jürgen A. Erhard eMail: [EMAIL PROTECTED] phone: (GERMANY) 0721 27326
My WebHome: http://members.tripod.com/Juergen_Erhard
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety." -- B. Franklin
PGP signature
Re: gimptool using --prefix for install?
On Tuesday, 1 Aug 2000, Alexander Skwar wrote: Can I somehow use gimptool to do this? I thought about something like "gimptool --prefix ~/tmp/prefix-dir --install-admin-bin pluginfile", and then gimptool should install "pluginfile" to "``~/tmp/prefix-dir''/usr/lib/gimp/1.1/plug-ins/", (without all those ",' `) but this obviously does not work. So, how can I find out where the plug-ins directory of gimp is? The --prefix idea for gimptool sounds like a good and useful feature. Some work needs to be done on gimptool before 1.2 can release. In particular, we need to be able to use it to automate the building of DLL modules without using a gimp build tree. Does anyone have skills in hacking it? Last time I looked it was a bit nightmarish. If there's no-one better qualified to hack it, then I will. But it won't be pretty :( Austin
