> Alexander Skwar:
> No, what I was thinking of, was it would be nice to be able to install a
> file in %{_mandir}, and that %{_mandir} would be expanded when the file is
> installed. Currently %{_mandir} may expand to /usr/man or /usr/share/man,
> depending on the distribution and version/relea
On Tue, Aug 08, 2000 at 05:14:45PM +0200, clemensF wrote:
> what do you mean by an install time macro? rpm's, but also tgz and the
> debian packager specify postinstall-scripts. you want propably a com-
> bination of this and automake?
No, what I was thinking of, was it would be nice to be able
> Alexander Skwar:
> > locations? For example, SuSE puts binaries for X in /usr/bin/X11. RPMs I've used
>to
> > upgrade apps keep putting X binaries in /usr/bin. (Is that the Red Hat standard?)
>
> And that's why an install time macro would be so handy. If this would be
> used, it wouldn't s
hi,
> Perl, PDL, Gimp und gtk-perl do work fine.
> I figured out, that the perl plugins only work if I start gimp
> as user root. I have no idea why...
possibly security...but I, of course, never run stuff as root ;-)
alan
In short form:
./configure --host=linux
In fuller form:
The instructions I referred to are now at
http://www.sderby.lug.org.uk/reviews/gimp/gimprev.html
They weren't meant to solve your perl problems though as they are intended as a
quick and simple way of installing the gimp for new users, ie
TED]>
Sent: Tuesday, August 08, 2000 9:26 AM
Subject: Re: GIMP v1.1.24 RPM Take 2
> Hi!
>
> Do you updated your compiler?
> At least this reulted for me in this error.
>
> Try using the configure option --target etc.
>
>
> --Joachim
>
> > Dom,
> >
> >
alled, but this message
still comes up.
regards,
Andrew
- Original Message -
From: DM Knight <[EMAIL PROTECTED]>
To: clemensF <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, August 08, 2000 1:06 AM
Subject: Re: GIMP v1.1.24 RPM Take 2
> You could also try
Am Mon, 07 Aug 2000 schrieben Sie:
> On Mon, Aug 07, 2000 at 11:48:20AM +0100, Alan Buxey <[EMAIL PROTECTED]> wrote:
> > 'specialised' and 'conventions' spell proprietary in my book.
> > whats wrong with the 'open' RPM standard embraced by the tools already on
> > most Linux, Solaris, Un8X system
On Mon, Aug 07, 2000 at 10:44:21AM -0400, Robb Kidd wrote:
> Isn't this mostly differences in a given distribution's choices about file
> locations? For example, SuSE puts binaries for X in /usr/bin/X11. RPMs I've used to
> upgrade apps keep putting X binaries in /usr/bin. (Is that the Red H
Marc Lehmann wrote:
> On Mon, Aug 07, 2000 at 11:48:20AM +0100, Alan Buxey <[EMAIL PROTECTED]> wrote:
> > 'specialised' and 'conventions' spell proprietary in my book.
> > whats wrong with the 'open' RPM standard embraced by the tools already on
> > most Linux, Solaris, Un8X systems?
>
> At least
On Mon, Aug 07, 2000 at 04:06:08PM +0100, DM Knight <[EMAIL PROTECTED]> wrote:
> I don't think gimp will configure with perl 5.6 as the config files point
The gimp (source) will configure with perl 5.6 for sure, but if and only if
perl5.6 is installed correctly. (It's not more difficult to instal
Hi!
On Mon, 7 Aug 2000, Alan Buxey wrote:
> cant help you more than saying I got source of Perl5.6.0 and Gimp 1.1.24
> and compiled both of them (after reading documents) and then installed PDL
> and gtk-perl afterwards (both taken from gimp's FTP site)
Perl, PDL, Gimp und gtk-perl do work fine
You could also try installing from source, I have attempted to knock together
some instructions and you will find a link to them at
http://www.sderby.lug.org.uk/
Sorry I cannot point directly as the site is being re-mapped.
I don't think gimp will configure with perl 5.6 as the config files poi
Unsubscribe me please ... I'm getting bored of low-level mails,thanks.
hi,
> Which additional pacckages do I need for the plugins to work?
> My perl plugins stopped working since version 1.1.19 of gimp.
> I compiled the source-distribution of perl-5.6.0 and installed
> - Parse-RecDescent-1.78
> - PDL-2.005
> - Gtk-Perl-0.6123
>
> Both perl and gimp compiled without
On Mon, Aug 07, 2000 at 11:48:20AM +0100, Alan Buxey <[EMAIL PROTECTED]> wrote:
> 'specialised' and 'conventions' spell proprietary in my book.
>
> whats wrong with the 'open' RPM standard embraced by the tools already on
> most Linux, Solaris, Un8X systems?
At least according to daniel egger,
Hi!
On Mon, 7 Aug 2000, Alan Buxey wrote:
> because you've chosen a non-standard PERL distribution. get 5.6.0 for the
> latest up-to-date PERL.
Which additional pacckages do I need for the plugins to work?
My perl plugins stopped working since version 1.1.19 of gimp.
I compiled the source-distr
hi,
> No, that was not what I meant. Mandrake RPMs are about all compiled with the
> same settings, use a standard way to update menus for GNOME or KDE and store
> files like manpages in the same location (/usr/share/man/*). So, if you're
> using a Mandrake distribution, it is best to stay with
TED]
Thema: Re: Antwort: Re: GIMP v1.1.24 RPM Take 2
hi,
> mdk rpms are specialized RPMs that conform to the Mandrake RPM conventions.
'specialised' and 'conventions' spell proprietary in my book.
whats wrong with the 'open' RPM standard embraced by the tools a
hi,
> mdk rpms are specialized RPMs that conform to the Mandrake RPM conventions.
'specialised' and 'conventions' spell proprietary in my book.
whats wrong with the 'open' RPM standard embraced by the tools already on
most Linux, Solaris, Un8X systems?
best avoid those 'special blands' and ke
mdk rpms are specialized RPMs that conform to the Mandrake RPM conventions.
hi,
> "error: failed dependencies:
> perl = 5.005_03 is needed by gimp-1.1.24-2
> /usr/lib/perl5/site_perl/5.005/i686-pld-linux-thread is needed by
> gimp-1.1.24-2
> gtk+ >= 1.2.8 is needed by gimp-1.1.24-2
> perl(Carp) is needed by gimp-1.1.24-2
> perl(DynaLoader) is needed by gimp-1.1.24-2
> Andrew J Fortune:
> Following up on a previous posting, I am still trying to install GIMP
> approach of installing an RPM.
>
> gimp-1.1.24-2.i686.rpm), I got the following errors :
> "error: failed dependencies:
> follows (rpm -Uvh gtk-1.2.8-24.i386.rpm), but got a long string of errors
> (rpm
Uninstall the other programs first, or do
rpm -ivh foo-bar.rpm --force
24 matches
Mail list logo
