Peter <peter@localhost.com> wrote:
> There is no slackware python installation per se. Each module provides
> it's own setup.py file. It's very generic and uses distutils to handle
> the behind the scenes work.

Pygtk ships with both a configure script and a setup.py. However, when
running setup.py you get a warning that distutils is not supported and
that setup.py is shipped only to support MS Windows installations.

> Everything else should just go where python is installed automatically.
> Exceptions being pygtk, pycairo, pygobject and other binding type
> libraries. They will drop files into the python directory, but you must
> use --prefix=/usr otherwise they will break.

Thanks for your reply. From this I can now tell that it is not the
Slackware python installation that is broken. Instead I consider pygtk to
be slightly broken as it doesn't work with default settings for configure
and giving the --prefix=/usr causes it to not be installed in /usr/local
as I would have prefered.

> Another thing, unlike using cpan (PERL), python generally does not
> install dependencies without your knowledge. It's possible your
> application was shipped with some but python would not generally fetch
> them.

No, ocfs2-tools did not fetch them for me. However, I am writing my own
makepack rules for pygtk and ocfs2-tools. Once I get them working I can
simply type:

make ocfs2-tools install

and watch it download, compile and install the application with all its
dependencies.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc1(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost