"Adam D. Moss" <[EMAIL PROTECTED]> writes:
> Michael Natterer wrote:
> >
> > Nick Lamb <[EMAIL PROTECTED]> writes:
> > > NB I am not blind and I don't write code in Hebrew
> >
> > I respect your extraordinary tolerance regarding this, so please
> > respect that the people actually working on a
Kelly Martin ([EMAIL PROTECTED]) wrote:
> On Fri, 27 Jul 2001 22:18:32 +0200, Lourens Veen <[EMAIL PROTECTED]> said:
> >I may be misunderstanding, I'm not a project expert, but if the Gtk
> >API is frozen, the only difference between the CVS HEAD branch and
> >the latest developer release is bugfi
On Fri, 27 Jul 2001 22:18:32 +0200, Lourens Veen <[EMAIL PROTECTED]> said:
>I may be misunderstanding, I'm not a project expert, but if the Gtk
>API is frozen, the only difference between the CVS HEAD branch and
>the latest developer release is bugfixes right?
No, because the HEAD branch could c
On Fri, 27 Jul 2001 22:18:32 +0200, Lourens Veen <[EMAIL PROTECTED]> said:
>I may be misunderstanding, I'm not a project expert, but if the Gtk
>API is frozen, the only difference between the CVS HEAD branch and
>the latest developer release is bugfixes right? So then there should
>be actually le
Kelly Martin wrote:
>
> Think "plugin authors". These people are going to want to start
> working on porting their plugins to 2.0 well in advance of 2.0's
> release but are not likely to want to cope with being GTK debuggers on
> top of being GIMP debuggers.
>
> Kelly
I may be misunderstanding
>I think we need to ask ourselves why users would want to try the
>latest developer releases of Gimp. If they want to have the latest
>because of having the latest, I don't think they'll mind getting CVS
>HEAD branches and weeding out possible compile problems.
Think "plugin authors". These peo
Michael Natterer wrote:
>
> Nick Lamb <[EMAIL PROTECTED]> writes:
> > NB I am not blind and I don't write code in Hebrew
>
> I respect your extraordinary tolerance regarding this, so please
> respect that the people actually working on a project tend to make the
> decisions.
Uh, that's pretty h
Alright, this is turning into a flamewar and that's the least productive
of all. Let me try to wrap up this discussion:
The question: Will the gimp-1.3 developer releases depend on Gtk-1.3
HEAD CVS, or do we make certain every gimp-1.3.x release compiles with
gtk-1.3.y?
Arguments for depending o
On 27 Jul 2001 21:30:01 +0200, Michael Natterer <[EMAIL PROTECTED]> said:
>Nick Lamb <[EMAIL PROTECTED]> writes:
>>NB I am not blind and I don't write code in Hebrew
>I respect your extraordinary tolerance regarding this, so please
>respect that the people actually working on a project tend to m
Nick Lamb <[EMAIL PROTECTED]> writes:
> NB I am not blind and I don't write code in Hebrew
I respect your extraordinary tolerance regarding this, so please
respect that the people actually working on a project tend to make the
decisions.
regards,
--Mitch
On Fri, Jul 27, 2001 at 09:54:41AM -0700, Seth Burgess wrote:
> As an occasional developer, I ran into a problem trying to get CVS pango
> working - errors on link with the qt libraries. Anyone else expereienced
> these? Not at my machine now, or I'd include the errors.
>
> I didn't see any
Hi,
Seth Burgess <[EMAIL PROTECTED]> writes:
> As an occasional developer, I ran into a problem trying to get CVS pango
> working - errors on link with the qt libraries. Anyone else expereienced
> these? Not at my machine now, or I'd include the errors.
>
> I didn't see any obvious switche
As an occasional developer, I ran into a problem trying to get CVS pango
working - errors on link with the qt libraries. Anyone else expereienced
these? Not at my machine now, or I'd include the errors.
I didn't see any obvious switches in the configure. I'm a bit annoyed that qt
is keeping
Hi,
[EMAIL PROTECTED] writes:
> > Please excuse this inconvenience and let's hope the new tarballs
> > work for you.
>
> Really bad idea. This means that there are two versions of 1.2.2
> floating around; one which build and one that doesn't. I'd REALLY
> suggest to update the version number
On Fri, Jul 27, 2001 at 02:12:05AM +0100, Nick Lamb wrote:
> On Thu, Jul 26, 2001 at 01:27:59AM -0400, Malcolm Tredinnick wrote:
> > For CVS gimp, it is definitely not a problem to require the current
> > bleeding edge GTK.
>
> Malcolm did you ask me first? If you didn't, how did you come to the
On 27 Jul, Sven Neumann wrote:
> Please excuse this inconvenience and let's hope the new tarballs
> work for you.
Really bad idea. This means that there are two versions of 1.2.2
floating around; one which build and one that doesn't. I'd REALLY
suggest to update the version number
Servus
Hi,
there has been a problem with the 1.2.2 tarballs that made the
build fail for people that don't have msgfmt (part of gettext)
installed. I have built new tarballs that should fix this
problem. Unfortunately some mirrors already have the old tarballs
and it will take some time for them to ca
Hi,
Austin Donnelly <[EMAIL PROTECTED]> writes:
> Oops. It doesn't build out of the box. D'oh!!!
> && rm -f $file && PATH=../src:$PATH -o $file lt.po
> /bin/sh: -o: command not found
> make[2]: *** [lt.gmo] Error 127
> make[2]: Leaving directory `/local/scratch/and1000/gimp/gimp-1.2.2/po-p
On , 27 Jul 2001, Sven Neumann wrote:
> ftp://ftp.gimp.org/pub/gimp/v1.2/v1.2.2/
>
> This release fixes a large bunch of bugs, adds a couple of
> new translations and features a complete rewrite of the
> help pages.
Oops. It doesn't build out of the box. D'oh!!!
[...]
creating libcolorsel_w
Hi,
GIMP 1.2.2 is finally out and still a hadjaha release.
ftp://ftp.gimp.org/pub/gimp/v1.2/v1.2.2/
This release fixes a large bunch of bugs, adds a couple of
new translations and features a complete rewrite of the
help pages.
Happy GIMPing
Sven
___
20 matches
Mail list logo
