Re: GIMP release: 2.8.10 request, OS X

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Thu, Dec 5, 2013 at 11:55 PM, Partha Bagchi <partha1b@xxxxxxxxx> wrote:
> Hi Jehan,
>
> I don't patch Gimp anymore. In the past I did due to issues with language
> UI, file size issues on Windows, etc. I feel that the source is quite mature
> and does not need patching.
>
> I started building the Windows version back during Gimp 2.7.1 when there
> were no betas available and also no 64-bit python. I also wanted a pure
> 64-bit build. So, I took it upon myself to learn how to build all the
> dependencies and build Gimp. Similarly, I started building the OSX version
> when there was no pure OSX version and I wanted to learn how to build an app
> for Mac, and hence McGimp.
>
> For your question 3a ( you have 3 twice ;) ) - I have always mentioned the
> plugins I consider useful for photography on my website. I am reproducing
> the list here for completeness - you can always get the latest list from my
> builds:
> 1.  G'MIC
> 2.  Simple Bilateral Blur (edge preserving smoothing)
> 3.  Save and Export
> 4.  Resynthesizer
> 5.  Refocus-it
> 6.  David's Batch Processor
> 7.  Exif-Browser
> 8.  Wavelet-Denoise
> 9.  Wavelet-Sharpen
> 10. Wavelet-Decompose
> 11. Texture Tiler
> 12. Fix Chromatic Aberration
> 13. Satequalizer (saturation equalizer)
> 14. Advance Unsharp Mask
> 15. Liquid Scaling (liquid rescale)
> 16. Separate+ (color management in Gimp)
> 17. Advanced Tone Mapping (faux HDR)
> 18. Recover Shadows and Highlights
> 19. ShellOut
> 20. BIMP
>
> For question 3b, nothing prevents me from working with you. I think I do
> bring whatever issues I find to everyone's attention here.
>
> Finally as far as IRC is concerned, I have absolutely nothing against it and
> would have loved to participate. However, I just don't have the time.
>
> All the above I am doing as a hobby and I told you why I started it. I have
> not stopped since I have heard from a lot of people that they like my builds
> with all the plugins in one place and the 64-bit builds.

Thanks for the answer. So your build is not a patched GIMP. The "only"
plus are the embedded plugins (not that it is not a nice addition, but
I mean there is no core change). So you have not much to lose to
participate to the OSX official build.
You definitely have some knowledge to share, as discussed in another
thread. You could help us by setting up a nice OSX build system, with
automatic builds, maybe even some nightly, etc.

But if you really wish to continue also your own build because of the
plugins (because I can imagine that we won't suddenly integrate that
many additional plugins to maintain upstream. We have already quite a
lot of work for too few people!), I see at least 2 ways for you:

1/ you may create a special plugin-only combo containing all these
additional plugins; and for the main program, you redirect your user
base to the upstream GIMP;

2/ you still make your full build of GIMP + plugins, using the same
build scripts that you helped create upstream. They will likely be a
very simplified, robust and automatic version of everyone's current
procedure.

However I see this, working with us can only spare your time, whatever
you decide.

Jehan

> Hope this helps.
>
> Please let me know if you have any questions.
>
> Thanks,
> Partha
>
>
>
> On Wed, Dec 4, 2013 at 10:28 PM, Jehan Pagès <jehan.marmottard@xxxxxxxxx>
> wrote:
>>
>> Hi again!
>>
>> On Thu, Dec 5, 2013 at 12:42 PM, Jehan Pagès <jehan.marmottard@xxxxxxxxx>
>> wrote:
>> > Hi,
>> >
>> > On Thu, Dec 5, 2013 at 11:50 AM, Partha Bagchi <partha1b@xxxxxxxxx>
>> > wrote:
>> >> Hi Sven,
>> >>
>> >> Have been away for the Thanksgiving holidays.:)
>> >>
>> >> On Sun, Nov 24, 2013 at 4:59 AM, scl <scl.gplus@xxxxxxxxx> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> today there was [bugreport] about outdated builds for OSX.
>> >>>
>> >>> One reason for not being able to provide an official GIMP 2.8.8.
>> >>> on OS X build were serious issues on OS X Mavericks, for instance
>> >>> the [showstopper in the Text tool]. These have been solved in
>> >>> the meantime (thanks especially to Simone Karin Lehmann, Michael
>> >>> Natterer and Daniel Sabo).
>> >>>
>> >>> Therefore I think we should bring out GIMP 2.8.10 soon,
>> >>> including an official OS X build (preferably also for some older
>> >>> OS X versions). As far as I know Claytons build is at the ready.
>> >>> All we need is a 2.8.10 bump, don't we?
>> >>>
>> >>> This situation shows us another weakness again:
>> >>> there are at least four people working on an OS X release:
>> >>> Clayton Walker, Simone Karin Lehmann, Partha Bagchi and
>> >>> David Evans (Macports), not to mention the (still active?) maintainer
>> >>> of the outdated Fink build and the various people building GIMP
>> >>> on their own Macs. All of them do it in their rare spare time.
>> >>> All of them struggle alone with the special build issues of GIMP
>> >>> on OS X, its dependencies and the API incompatibilities between the
>> >>> various OS X versions.
>> >>> Can you guys and girls please find a way to work together?
>> >>> What makes it so hard to speak to another at the mailing list or IRC
>> >>> and unite your forces? Come on, we don't bite ;-)
>> >>>
>> >> Thanks for mentioning me. :)
>> >>
>> >> I am happy to collaborate with anyone on my builds. Note that I build
>> >> Gimp
>> >> and all dependencies from scratch using OSX gcc version 4.2.1; that is,
>> >> I
>> >> build gtk+, glib, pango, cairo etc. etc. etc. and then I build Gimp. I
>> >> also
>> >> include plugins that I believe are useful to photographers, well at
>> >> least
>> >> useful to me.
>> >
>> > This would be very nice.
>> > I have a few questions:
>> > 1/ Do you patch GIMP? Is it the reason why you make your own GIMP
>> > build? If so, would you please contribute us all your patches? We
>> > would be happy to check them and see what can be merged in our own
>> > source. We are already working on merging some of Simone Karin
>> > Lehmann's patches to improve our OSX code.
>> > 2/ Do you patch some of the third parties? GTK+, glib, etc. If so,
>> > have you tried to contributing upstream to these various projects?
>> > 3/ What is exactly the list of plugins you include in your build?
>> > 3/ Is there anything else which would prevent you to work with us on
>> > delivering a robust upstream OSX build (faster than currently after a
>> > source release!) instead of duplicating the work? Note that we have
>> > obviously nothing about third party builds. If you really wish to, you
>> > can still make your own builds (maybe slightly different), even though
>> > you would help us making the upstream one. But even so, this could
>> > profit to all of us, for instance by sharing build systems, thus
>> > improving the procedure.
>> > Ideally we could automatize all builds for very easy and early release!
>> >
>> > The way I see it, if we find a way to automatize builds, then we could
>> > generate them on a server with no further human input, and available
>> > for testers, which would make releases very easy to test (and
>> > regenerate in case of issue) before any release.
>>
>> By the way! Since you also maintain a Windows build, all above
>> questions would also pertain to your Windows build!
>>
>> Jehan
>>
>> >> Finally, it's not really feasible for me to come to IRC and hence I
>> >> loose
>> >> out on some of those discussion.
>> >
>> > Why is that? As I said to Simone too, I am not fond of IRC myself and
>> > probably don't connect as much as the other contributors, but I make
>> > some time to hang around there. If this is the price of collaboration,
>> > it is not too high. Or is that a technical impossibility? (behind some
>> > port-blocking firewall in a company or something?)
>> >
>> > Thanks!
>> >
>> > Jehan
>> >
>> >>>
>> >>> Thanks in advance,
>> >>>
>> >>> Sven
>> >>>
>> >> Thanks again,
>> >> Partha
>> >>
>> >>>
>> >>> [bugreport]:
>> >>> https://bugzilla.gnome.org/show_bug.cgi?id=715094
>> >>>
>> >>> [showstopper in the Text tool]:
>> >>> https://bugzilla.gnome.org/show_bug.cgi?id=711281
>> >>> _______________________________________________
>> >>> gimp-developer-list mailing list
>> >>> List address:    gimp-developer-list@xxxxxxxxx
>> >>> List membership: https://mail.gnome.org/mailman/listinfo/gimp-
>> >>> developer-list
>> >>>
>> >> _______________________________________________
>> >> gimp-developer-list mailing list
>> >> List address:    gimp-developer-list@xxxxxxxxx
>> >> List membership:
>> >> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
>
>
_______________________________________________
gimp-developer-list mailing list
List address:    gimp-developer-list@xxxxxxxxx
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list





[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux