Re: [Gimp-developer] Re: reporting bugs on builds

[David Neary]

Hi Jernej,

Jernej Simon?i? wrote:
 Not sure about what kind of proprietary scripts are you talking about - the
 installer scripts were always available...

I'm glad you joined the thread, because there's one question that
hasn't been answered yet.

Would you like to have your installer's problems tracked in
bugzilla? Or would you prefer us to refer the bug reporters to
your page? If so, where should we send them?

Cheers,
Dave.

-- 
   David Neary,
   Lyon, France
  E-Mail: [EMAIL PROTECTED]
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Re: reporting bugs on builds

[Sven Neumann]

Hi,

=?Windows-1250?Q?Jernej_Simon=E8i=E8?= [EMAIL PROTECTED] writes:

  Because we can't do anything about the bugs. Nobody but the packager
  can. The situation would be different if the tools used to build the
  binary packages would be in GNOME CVS. That would certainly qualify
  the project for also using the bug tracker. But as long as people
  build GIMP using proprietary scripts that they don't publish anywhere,
  I am going to show no tolerance towards them.
 
 Not sure about what kind of proprietary scripts are you talking about - the
 installer scripts were always available, though it depended a lot on my mood
 where I put them (in a separate zipfile, or together with the rest of
 sources). The setup compiler itself is free, too.
 
 To compile Gimp, I use MinGW+MSys, with no special tools.

I was under the impression that building a GIMP installer involved
some black magic. After all there don't seem to be many people able to
build GIMP from source on win32.

Perhaps the setup scripts should be kept in CVS then. Not sure if they
belong to the GIMP source, probably not. But there could be a separate
module.


Sven

___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer