Re: Using python + pygtk in Desktop modules

["Gustavo J. A. M. Carneiro" <gjc inescporto pt>]

Ter, 2004-09-28 às 13:26 -0400, Sean Middleditch escreveu:
> On Tue, 2004-09-28 at 18:13 +0200, Danilo Šegan wrote:
> > Hi Sean,
> > 
> > Today at 16:50, Sean Middleditch wrote:
> > 
> > > And it's not just packages, it's any app.  GNOME is great for third-
> > > party developers because they can just push out their app in a (mostly)
> > > LSB RPM or a tarball or automatic installer or Autopackage or whatever,
> > > and have it Just Work(tm), because the GNOME ABI is stable and you know
> > > for sure that any distro with the version you targeted or higher can run
> > > the app.  This makes third-party packages for GNOME apps actually
> > > feasible without needing a massive compile farm or expecting users to
> > > compile from source.
> > 
> > The current practice is *still* to have suitable packages for each
> > architecture, distribution, and distribution release.  So, you're
> > basically talking about a pipe-dream, and trying to convince us that
> > it's not possible with Python (while in practice, it's not being done
> > even with stable GNOME C libraries).
> 
> Yes, actually, it *is* being done.  Look at the Autopackage project, at
> the distro-independent Mozilla or OOo packages/installers, at various
> commercial apps that install with loki_setup or some other installer,
> and so on.
> 
> The stable C ABI *is* used, and works great.  And it works because of a
> "pipe dream" that people actually worked on, instead of taking your
> approach and going, "oh, things aren't perfect right now, so forget
> trying to make it better." (yes, that was over-dramatized - no offense
> meant, Murray.)

  Actually, autopackage is a good example.  They have to make some
tricks to workaround ABI changes in glibc. See here:
	http://www.autopackage.org/downloads.html

"
   Have you ever seen the "undefined symbol GLIBC_2.3 in /lib/libc.so"
error message? That's because an application or library was compiled for
glibc 2.3 and uses symbols which your (older) version of glibc doesn't
have. apbuild is a wrapper around gcc and allows you to compile
applications and libraries that do not use glibc 2.3 symbols. Your
application or library will work on current systems and most slightly
older systems.
"

  That just goes to show that in C things are not that good, ABI wise.

  Regards.

-- 
Gustavo J. A. M. Carneiro
<gjc inescporto pt> <gustavo users sourceforge net>
The universe is always one step beyond logic.