o included. The necessitates putting 'export DESTDIR' in the Makefile
so that it is passed to gimptool in the environment.
Regards,
Roger
*** gimptool.in Tue Jan 30 22:54:39 2001
--- ../gimp-orig/gimptool.inMon Jan 29 19:05:41 2001
***
*** 263,269
shift
Dear all,
I have the following concern with `gimptool':
[taken from my mail to [EMAIL PROTECTED]]
Problem: when gimptool is used in install-libexecPROGRAMS, it does not
allow the use of DESTDIR like all of the other install commands in the
makefile. The --prefix option to it has no effect
ir 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 lon
On Wed, Aug 02, 2000 at 09:22:45AM -0400, Robert L Krawitz <[EMAIL PROTECTED]> wrote:
> 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.
I'd say gimp itself lacks
ofiles, 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 d
re 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-d
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 l
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-speci
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 v
Date: Tue, 1 Aug 2000 09:34:10 -0400
From: Zachary Beane <[EMAIL PROTECTED]>
This was a legitimate screw-up in one version of Red Hat, IIRC. They
did not include the gimptool script in either gimp or gimp-devel
RPMs. This became an issue on IRC for several people, until we f
> "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 di
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/p
On Tue, Aug 01, 2000 at 11:31:42PM +0200, Marc Lehmann wrote:
>
> 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
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.
Why is that every program has to be "fixed" to be usable with rpm, and
ev
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 some
Robert L Krawitz wrote:
> A number of our users who are using Red Hat (6.0 or 6.2) report that
> there is no gimptool present with Gimp 1.0.4 (they've done a find and
> come up with nothing; they've checked that they've installed
[snip]
> Any suggestions? Is R
On Tue, Aug 01, 2000 at 03:42:35PM +0200, Simon Budig
<[EMAIL PROTECTED]> wrote:
> > I don't think so: You don't need header files to add a plug-in. You only
> > need gimptool. The header files are only required when compiling a plug-in
> > from source.
>
&g
On Tue, Aug 01, 2000 at 09:34:10AM -0400, Zachary Beane wrote:
> This was a legitimate screw-up in one version of Red Hat, IIRC. They
> did not include the gimptool script in either gimp or gimp-devel
> RPMs. This became an issue on IRC for several people, until we finally
> fi
navailable.
>
> I don't think so: You don't need header files to add a plug-in. You only
> need gimptool. The header files are only required when compiling a plug-in
> from source.
So you can obtain precompiled plugins from the registry?
Anyway. I am not really happy a
This was a legitimate screw-up in one version of Red Hat, IIRC. They
did not include the gimptool script in either gimp or gimp-devel
RPMs. This became an issue on IRC for several people, until we finally
figured it out.
Zach
--
[EMAIL PROTECTED] Zachary Beane http://www.xach.com/
On Tue, Aug 01, 2000 at 02:26:49PM +0200, Simon Budig
<[EMAIL PROTECTED]> wrote:
> impossible w/o gimp-devel, because the libgimp header files are
> unavailable.
Also, gimptool is very useful for other programs, to find out where gimp
was installed, eve
er files to add a plug-in. You only
need gimptool. The header files are only required when compiling a plug-in
from source.
--
-==- |
==-- _ |
---==---(_)__ __ __
Perhaps have the users run rpm -ql gimp-devel | grep gimptool.
Alan
Marc Lehmann ([EMAIL PROTECTED]) wrote:
> On Tue, Aug 01, 2000 at 11:49:26AM +0200, Simon Budig
><[EMAIL PROTECTED]> wrote:
> > IIRC gimptool is in the gimp-devel package, which makes sense, because
> > all uses (except determining the Gimp Version) are developer-related.
ote:
> > Any suggestions? Is Red Hat broken, or is it our configure script?
>
> Obviously, if gimptool is missing the rpm source (e.g. the distro) is
> broken, as is the usual case.
Most likely the users have not installed the gimp-devel package.
They claim to have done so.
On Tue, Aug 01, 2000 at 11:49:26AM +0200, Simon Budig
<[EMAIL PROTECTED]> wrote:
> IIRC gimptool is in the gimp-devel package, which makes sense, because
> all uses (except determining the Gimp Version) are developer-related.
So, adding scripts you downloaded from the registry
On Tuesday, 1 Aug 2000, Marc Lehmann wrote:
> On Mon, Jul 31, 2000 at 09:29:01PM -0400, Robert L Krawitz <[EMAIL PROTECTED]> wrote:
> > Any suggestions? Is Red Hat broken, or is it our configure script?
>
> Obviously, if gimptool is missing the rpm source (e.g. the distr
Robert L Krawitz ([EMAIL PROTECTED]) wrote:
[gimptool not in Red Hat Gimp RPM]
> Any suggestions? Is Red Hat broken, or is it our configure script?
IIRC gimptool is in the gimp-devel package, which makes sense, because
all uses (except determining the Gimp Version) are developer-related.
On Mon, Jul 31, 2000 at 09:29:01PM -0400, Robert L Krawitz <[EMAIL PROTECTED]> wrote:
> Any suggestions? Is Red Hat broken, or is it our configure script?
Obviously, if gimptool is missing the rpm source (e.g. the distro) is
broken, as is the usual case.
You might want to find out
A number of our users who are using Red Hat (6.0 or 6.2) report that
there is no gimptool present with Gimp 1.0.4 (they've done a find and
come up with nothing; they've checked that they've installed
gimp-devel). However, it appears to be present in at least some
places w
Hi,
> if I want to build a plug-in with gimptool from 1.1.23, I get for
> example
>
> ps.c:62: config.h: No such file or directory
> ps.c:74: libgimp/stdplugins-intl.h: No such file or directory
>
> gimptool --cflags
>
> gives me
>
> -I/usr/local/lib/glib/in
Hi,
if I want to build a plug-in with gimptool from 1.1.23, I get for
example
ps.c:62: config.h: No such file or directory
ps.c:74: libgimp/stdplugins-intl.h: No such file or directory
gimptool --cflags
gives me
-I/usr/local/lib/glib/include -I/usr/local/include -I/usr/X11R6/include
ight, but they can be made compatible at the source level with a very
> small amount of #ifdef'age. It's important for build scripts.
gimptool --install-admin-bin foo-plugin
That's how I install the plugin, yes.
> That's the right idea, although /usr/local/shar
e made compatible at the source level with a very
> small amount of #ifdef'age. It's important for build scripts.
gimptool --install-admin-bin foo-plugin
>>What do you need exactly? We could extend gimptool to provide values
>>for the whole gamut of au
What do you need exactly? We could extend gimptool to provide values
>for the whole gamut of autoconf installation path variables...
>
> The print plugin will at some point have auxiliary files. I'm
> thinking of moving the printer descriptions out of the plugin (wh
e: Fri, 3 Mar 2000 11:49:14 -0800
>>From: Manish Singh <[EMAIL PROTECTED]>
>>
>>gimptool --prefix and gimptool --exec-prefix will give you these dirs.
>>
>> All they give me is /usr/local; they don't tell me where the Gimp is
>
Date: Fri, 3 Mar 2000 17:44:55 -0800
From: Manish Singh <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
On Fri, Mar 03, 2000 at 08:48:29PM -0500, Robert L Krawitz wrote:
>Date: Fri, 3 Mar 2000 11:49:14 -0800
>From: Manish Singh <[EMAIL PROTECTED]>
&
On Fri, Mar 03, 2000 at 08:48:29PM -0500, Robert L Krawitz wrote:
>Date: Fri, 3 Mar 2000 11:49:14 -0800
>From: Manish Singh <[EMAIL PROTECTED]>
>Cc: [EMAIL PROTECTED]
>
>On Fri, Feb 25, 2000 at 08:38:51AM -0500, Robert L Krawitz wrote:
>> Gimptool
Date: Fri, 3 Mar 2000 11:49:14 -0800
From: Manish Singh <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
On Fri, Feb 25, 2000 at 08:38:51AM -0500, Robert L Krawitz wrote:
> Gimptool has no specific way to echo the name of the Gimp installation
> directory. There are
On Fri, Feb 25, 2000 at 08:38:51AM -0500, Robert L Krawitz wrote:
> Gimptool has no specific way to echo the name of the Gimp installation
> directory. There are options for installing things, for getting
> flags, and such, but nothing to simply report where the Gimp is
> install
Robert L Krawitz wrote:
>
>($plugins = `$GIMPTOOL -n --install-admin-bin /bin/sh`) =~
>s{^.*\s(.*?)(?:/+bin/sh)\r?\n?$}{$1}}
>
> Which will work for essentially any general purpose Linux system,
> since every distribution I know of comes with perl, but...
FWIW, I do ever
Date: Fri, 3 Mar 2000 11:54:48 +0100
From: Marc Lehmann <[EMAIL PROTECTED]>
($plugins = `$GIMPTOOL -n --install-admin-bin /bin/sh`) =~
s{^.*\s(.*?)(?:/+bin/sh)\r?\n?$}{$1}}
(I only need it in the testsuite, which is not run when we're inside the
gimp source tree)
On Fri, Feb 25, 2000 at 08:38:51AM -0500, Robert L Krawitz <[EMAIL PROTECTED]> wrote:
> Gimptool has no specific way to echo the name of the Gimp installation
For backwards compatibility, with 1.0 I use
($plugins = `$GIMPTOOL -n --install-admin-bin /bin/sh`) =~
s{^.*\s(.*?)(?:/+bin
Gimptool has no specific way to echo the name of the Gimp installation
directory. There are options for installing things, for getting
flags, and such, but nothing to simply report where the Gimp is
installed.
The issue here is that I'd like change the printer descriptions inside
the
44 matches
Mail list logo
