Re: [Gimp-developer] Portable development environment for GIMP

2015-09-28 Thread Sam Gleske
On Mon, Sep 28, 2015 at 11:10 AM, Michael Schumacher 
wrote:

>
>
> On 09/28/2015 07:30 PM, Sam Gleske wrote:
> > On Mon, Sep 28, 2015 at 10:21 AM, Michael Schumacher 
> > wrote:
> >> Um... why is KDE in there?
> >>
> >
> > I realize KDE is not everyone's preference in UI.  What UI do you and
> other
> > core developers use?
>
> I'd say that we should stick to something that has the same basic
> dependencies as GIMP - XFCE, for example.
>
>
+mailing list

XFCE would definitely lighten the load in terms of number of dependencies.
UI aside, any feedback on how I'm building GIMP?  Have you tried spinning
up the development environment?  Is it able to build GIMP like one would
expect?

Should I have it auto-build GIMP for the first time as part of the
bootstrapping?


-- 
I prefer to encrypt my email

GPG FINGERPRINT 4096 KEY
8D8B F0E2 42D8 A068 572E
BF3C E8F7 3234 7257 E65F
https://keybase.io/samrocketman

Learn how to encrypt your email with the Email Self Defense guide:
https://emailselfdefense.fsf.org/en/
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Portable development environment for GIMP

2015-09-28 Thread Sam Gleske
On Mon, Sep 28, 2015 at 11:17 AM, Pat David  wrote:

> Maybe GNOME?. :)
>

It could be provided as an option.  KDE is what I use typically during
development which is why I set it.  However, setting it to something more
light weight like XFCE by default makes sense in terms of being able to get
right in and develop.


-- 
I prefer to encrypt my email

GPG FINGERPRINT 4096 KEY
8D8B F0E2 42D8 A068 572E
BF3C E8F7 3234 7257 E65F
https://keybase.io/samrocketman

Learn how to encrypt your email with the Email Self Defense guide:
https://emailselfdefense.fsf.org/en/
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Portable development environment for GIMP

2015-09-28 Thread Michael Schumacher


On 09/28/2015 08:22 PM, Ofnuts wrote:

> Plenty of UIs and desktop managers, and plenty of development tastes...
> I'm myself on KDE, but if your VM was running Gnome or Unity, it would
> be useless to me. I do use a VM for some development that can only be
> done on Windows, but using a Linux VM over my existing Linux install is
> a bit wasteful?

A good idea would be to use a DE that has the same dependencies as GIMP
- XFCE comes to mind, as it is also likely the least demanding
environment of all mentioned so far, and still reasonably sophisticated.


-- 
Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Portable development environment for GIMP

2015-09-28 Thread Sam Gleske
On Mon, Sep 28, 2015 at 10:21 AM, Michael Schumacher 
wrote:

>
>
> On 09/27/2015 08:35 PM, Sam Gleske wrote:
>
> >1. Install vagrant https://www.vagrantup.com/
> >2. Clone: git clone https://github.com/samrocketman/vagrant-gimp
>
> Um... why is KDE in there?
>
>
Because it's a UI.  Would you rather build headless?


-- 
I prefer to encrypt my email

GPG FINGERPRINT 4096 KEY
8D8B F0E2 42D8 A068 572E
BF3C E8F7 3234 7257 E65F
https://keybase.io/samrocketman

Learn how to encrypt your email with the Email Self Defense guide:
https://emailselfdefense.fsf.org/en/
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Portable development environment for GIMP

2015-09-28 Thread Pat David
Maybe GNOME?. :)
On Mon, Sep 28, 2015 at 1:23 PM Sam Gleske  wrote:

> On Mon, Sep 28, 2015 at 10:21 AM, Michael Schumacher 
> wrote:
>
> >
> >
> > On 09/27/2015 08:35 PM, Sam Gleske wrote:
> >
> > >1. Install vagrant https://www.vagrantup.com/
> > >2. Clone: git clone https://github.com/samrocketman/vagrant-gimp
> >
> > Um... why is KDE in there?
> >
> >
> Because it's a UI.  Would you rather build headless?
>
>
> --
> I prefer to encrypt my email
>
> GPG FINGERPRINT 4096 KEY
> 8D8B F0E2 42D8 A068 572E
> BF3C E8F7 3234 7257 E65F
> https://keybase.io/samrocketman
>
> Learn how to encrypt your email with the Email Self Defense guide:
> https://emailselfdefense.fsf.org/en/
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Portable development environment for GIMP

2015-09-28 Thread Ofnuts

On 28/09/15 19:22, Sam Gleske wrote:

On Mon, Sep 28, 2015 at 10:21 AM, Michael Schumacher 
wrote:



On 09/27/2015 08:35 PM, Sam Gleske wrote:


1. Install vagrant https://www.vagrantup.com/
2. Clone: git clone https://github.com/samrocketman/vagrant-gimp

Um... why is KDE in there?



Because it's a UI.  Would you rather build headless?



Plenty of UIs and desktop managers, and plenty of development tastes... 
I'm myself on KDE, but if your VM was running Gnome or Unity, it would 
be useless to me. I do use a VM for some development that can only be 
done on Windows, but using a Linux VM over my existing Linux install is 
a bit wasteful?




___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Portable development environment for GIMP

2015-09-28 Thread Michael Schumacher


On 09/28/2015 08:40 PM, Sam Gleske wrote:

> FUTURE:
> Even when I maintain the build system at build.gimp.org there's regularly a
> "works for me" statement when the build system fails but it passes on a
> developers laptop.  These challenges hinder progress when having a
> repeatable build environment would solve these issues.

GIMP developers use Debian Testing, with the assumption that is anything
is present there, then a GIMP build can require it.

A build based on Debian Jessie, currently aka Debian Stable, will divert
from that over time, and might not even contain some of the required
dependencies. Due to the recent release of Jessie, this is not very
noticeable yet.

A moving target like Debian Testing is probably a less than optimal
building block for a vagrant-based approach.

-- 
Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Portable development environment for GIMP

2015-09-28 Thread Michael Schumacher


On 09/27/2015 08:35 PM, Sam Gleske wrote:

>1. Install vagrant https://www.vagrantup.com/
>2. Clone: git clone https://github.com/samrocketman/vagrant-gimp

Um... why is KDE in there?


-- 
Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Portable development environment for GIMP

2015-09-28 Thread Sam Gleske
On Mon, Sep 28, 2015 at 11:22 AM, Ofnuts  wrote:

>
> Plenty of UIs and desktop managers, and plenty of development tastes...
> I'm myself on KDE, but if your VM was running Gnome or Unity, it would be
> useless to me. I do use a VM for some development that can only be done on
> Windows, but using a Linux VM over my existing Linux install is a bit
> wasteful?


In this case, it is not wasteful.  Consider the goals of this project (and
development from the perspective of a newcomer).

NEWCOMER PERSPECTIVE:
* Must assemble over 100 dependency packages from Debian (for Debian
GNU/Linux alone; not including other platforms).
* Must clone two additional projects (GEGL and BABL).
* Must compile projects in the correct order: 1) BABL 2) GEGL 3) GIMP.
* On the mailing list there's a lot of "works for me, so it must be
something wrong with what you're doing"

The point of a bootstrapped development environment is to avoid even having
to answer most of the above questions before they're even asked.

PRIMARY GOALS:
* Lower the barrier to entry for contributing to GIMP source code.
* Repeatable and consistent configuration between someone who is new and
someone who can verify if issues experienced by the new contributor is with
the development environment or with GIMP itself.

FUTURE:
Even when I maintain the build system at build.gimp.org there's regularly a
"works for me" statement when the build system fails but it passes on a
developers laptop.  These challenges hinder progress when having a
repeatable build environment would solve these issues.

Future-looking action items for me that will come out of this:
* Containerize (via docker) a build environment based off of the vagrant
bootstrap development environment.  This means build.gimp.org will run the
same code and dependencies as the development environment.  Avoids the
"works for me" syndrome between core developers and the build system.
* Create a Windows-based development environment based on
https://atlas.hashicorp.com/modernIE and https://dev.modern.ie/ (free
Windows VMs provided by Microsoft).

CONCLUSION:
By settling on a convention for how we build the GIMP software we'll:
* speed up development velocity
* be more consistent
* have a lower barrier to entry for new contributors

SAM

-- 
I prefer to encrypt my email

GPG FINGERPRINT 4096 KEY
8D8B F0E2 42D8 A068 572E
BF3C E8F7 3234 7257 E65F
https://keybase.io/samrocketman

Learn how to encrypt your email with the Email Self Defense guide:
https://emailselfdefense.fsf.org/en/
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list