Dan Nicholson wrote these words on 08/08/07 13:01 CST: > On 8/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Log: >> Modified the Gnome-Python dependency list entity (use this until >> Gnome-Python is put in the book) > > What's the plan for gnome-python?
To put it in the book. > I think pygtk should definitely be > in the book. I think we should turn the PyXML page into a 'Python modules' page similar to the 'Perl Modules' page. Almost every Python module is "setup.py install" or CMMI. A blanket page for all modules should be really easy. > For gnome-python and gnome-python-desktop, I think it > will be a good idea if we attempt to enumerate them by module so that > people can attempt to avoid some extreme dependency hell. > > gnome-python: > Required: pygtk and libgnome > Required (for gnome.ui module): pyorbit and libgnomeui > Required (for gnome.canvas module): libgnomecanvas > Required (for gnomevfs module): gnome-vfs Yeah, this looks good. We do this on many pages, so it isn't anything out of the ordinary. > Then, for GNOME Applets, for instance (not necessarily true): > <xref linkend="gnome-python"/> (gnomevfs module), <xref > linkend="gnome-python-desktop/> (gnomeprint module) > > What do you think? Looks good to me. I just wish it was already done, though. I'm tired of messing with GNOME. KDE is so much better (it is also much easier). -- Randy rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 13:11:00 up 6 days, 13:02, 1 user, load average: 1.11, 0.94, 0.53 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
