Add Missing dependency intltool

[srevinsaju]

Dependency intltool was missing from Documentation

[Aniket21mathur]

I don't think explicitly defining intltool as a dependency is a good idea. It gets installed once you build dependencies for sugar. Though I will like to know what others think.

What is the error that you got?

[aperezbios]

I completely disagree. All build dependencies should be explicitly laid out. Nothing should be assumed, including in this case.

[srevinsaju]

@Aniket21mathur
This is the error:
intltoolize: command not found

[quozl]

Thanks. I agree with both @Aniket21mathur and @aperezbios. Please complete the list of dependencies before making a commit. See my comment in #884.

[Aniket21mathur]

This is the error:
intltoolize: command not found

Thanks, noted. Clearly indicates that the dependencies are not built before installing. Please build before installing. :-)

[srevinsaju]

Seems like I have got the list of rudimentary dependencies required for running sugar on any platform:

• espeak
• gtksoureview3
• gvfs
• libwnck3 or libwnck
• libxklavier
• metacity
• openssh
• telepathy-mission-control
• cairo
• python-cairo
• pygame
• python-xapian
• python-gobject (Arch and other pacman based) python-gi (Ubuntu / Fedora)
• python-dbus
• gtk2
• python-dateutil
• icon-naming-utils
• python-decorator
• telepathy-gabble
• telepathy-salut
• upower
• webkitgtk2
• xdg-user-dirs
• python-six
• libsm
• unzip
• alsa-lib
• xorg-xcursorgen

Looking forward for comments and corrections, I will add on if more are found.
Please review @quozl @aperezbios

[quozl]

Thanks.

But that looks like an Arch list, and it is not correct for Debian or Fedora. If we're going to maintain them, the dependencies must be listed in a form that is not distribution specific. I said this earlier in #884.

They also have to form part of the commit, not as a pull request comment.

You can find the downstream dependencies on Fedora by looking at the .spec file, and on Ubuntu by looking at the debian/control file.

We used to maintain platform components as a set of dependencies of Sugar and assumed to be present dependencies for activities. That effort died.

[srevinsaju]

should the list be something like this
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Install_the_dependencies

[quozl]

No. Like our previous platform components page, using the formal project name for each dependency. After that we could add distribution-specific package names, but those names rarely match the formal project name. Also, the formal project names rarely change, but distributions often change the package name from release to release.