On Mon, Dec 15, 2003 at 11:58:10PM -0500, John (J5) Palmieri wrote:
> > The main confussion pygtk make is about its name. I have seen
> > pygtk, pygnome, pyglade, python-gtk, python-gnome and python-glade.
> > I am a debian user and I have Installed python2.3-glade. What
> > exactly is the relation between all these?. I think it need to be
> > cleraly mentioned in our site too.
> > (Sorry if this question is already answered some where else)
>
> As a Debian user perhaps I can answer this for you. The "problem" is
> more with Debian, if you can call it a problem. Debian names their
> packages according to their own naming conventions. Most of the time
> this corrasponds to the upstream package name but sometimes it doesn't.
> Also debian users tend to want tight control over what is installed on
> their computers so they split up the gnome python packages into
> multipule packages. This might be a pain sometimes but it ensures that
> if your programs don't use python's glade bindings you don't need to
> have them installed. This is important for resource strained
> enviornments. Debian also has the libraries packaged for different
> python versions. So in your case python2.3-glade are the glade bindings
> (libglade to be exact) for python version 2.3.
I'm also a Debian user, and I can understand that the naming can cause
some confusion. The thing to keep in mind is that the "official"
pygtk-related *products* (which would be endorsed by what could become
"pygtk.org" <wink>) are pygtk, gnome-python (which includes, and
there for is a superset of, pygtk) and pyorbit. These products are
distributed in tarballs, in source form (with a .tar.gz or .tar.bz2
suffix).
Distributions take these products, then split and rename them --
according to their own guidelines (usually strict separation of
developer and user contents, grouping of related functionality, etc) --
into distribution packages (with suffixes such as .deb and .rpm).
Let's use those names, products and packages, to differentiate between
them.
And now re-summarizing, for Debian:
- All Python packages are prefixed by python.
- python-gtk corresponds to the pygtk product, minus the
libglade-dependent bits (see below).
- python-gnome corresponds roughly to the GNOME-specific bits of
the gnome-python product. Some confusion arises here because the
gnome-python CVS module and release tarballs contain pygtk too --
the python-gnome deb includes only the GNOME-specific bindings.
- python-glade corresponds to the libglade-specific bits of pygtk.
- pygnome, pygtk and pyglade seem to be aliases for python-gnome,
python-gtk and python-glade, respectively (but only pygnome exists
in Woody).
- python-pyorbit corresponds to the "official" pyorbit package.
(- python-orbit corresponds to the old orbit-python product that
Jason Tackaberry wrote (and Johan, Roland and I hacked) and which
is now pretty much dead. In turn, *this* replaced the original
(dead by 2001) PyORBit -- and note that this last product is
unrelated to the recent PyORBit product (mostly written by James
IIRC). If you're confused (you should be), forget all this
nonsense and just trust me that you want python-pyorbit.)
- the X.X version number that comes after the "python" prefix
indicates what version of Python that package was generated for --
python versions have some measure of binary compatibility between
versions, but they are essentially version-specific and that's why
we have multiple versions of the same package for different
Pythons.
See, like I always say, it's simple! <wink>
Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
