Id say remove the bootstrap command/moduleset completely

(In reply to comment #1)
> Id say remove the bootstrap command/moduleset completely

JHBuild should provide assistance if the user's distro autotools aren't recent enough. Or autotools not the correct version (autotools can be fussy with version, but this has settled down recently).

I'd be in favour of 'remove bootstrap. Build autotools if required' design.

There are some modules that should really come from distribution packages, or you won't see the end of it, especially as you'll have to venture with non-autotools build systems as you go down the stack.

In the particular case of Python, I'd say that it should be removed from the bootstrap moduleset.

Integrating/merging/whatever bootstrap and sysdeps would be the subject of another bug report.

(In reply to comment #3)
> In the particular case of Python, I'd say that it should be removed from the
> bootstrap moduleset.

And happy if Python was added to GNOME modulesets?

I opened bug 656818 to deal with getting rid of all of bootstrap.

IMHO we shouldnt build python ourselves to build GNOME, we have to relay in the current installed version in the system (the same way we dont compile gcc).
So my vote is to remove python completely from the modulesets.

I am with Javier on this one.

If remove python then developers on Debian 5 lenny & Red Hat EL 5 can't build GNOME 3.2 [1].

Debian 6 & Red Hat EL 6 have only been released in the approximately last 6 months.

My preference is to add Python to the moduleset and use sysdeps. If Python's needed, it's built, otherwise it's not.

[1] without manually building python themselves.

Well, if we care about old distributions, we shouldn't let a module depend on Python 2.6. I really do not want to have Python in the common list of modules to be build and installed.

I have another idea that we may be able to agree on. I'll propose the idea in bug 656818. Closing this bug.