random ramblings from some random dude
diary of a window system hacker

About

Daniel Stone
X ninja
Helsinki, FI

Planets

Planet freedesktop.org
Planet GNOME
Moon Debian

Organisations

challenge
children's cancer centre, rch
ecoles sans frontières
amnesty international
engineers without borders australia
ikando
australian greens
australian republican movement

Links

my website
my photos at flickr
x.org
linux.conf.au 2008
eat.fi
Open Source Food

Categories

/ (125)
  site/ (3)
  tech/ (119)
    debian/ (10)
    fdo/ (15)
    kde/ (1)
    lca/ (1)
    ubuntu/ (10)
    x/ (49)
      xds/ (3)
  travel/ (3)
    guadec2007/ (1)


Archives

2008-Aug
2008-Jul
2008-Jun
2008-May
2008-Feb
2007-Oct
2007-Sep
2007-Jul
2007-Jun
2007-May
2007-Mar
2007-Jan
2006-Nov
2006-Aug
2006-Jun
2006-May
2006-Apr
2006-Mar
2006-Feb
2006-Jan
2005-Dec
2005-Nov
2005-Oct
2005-Sep
2005-Aug
2005-Jul
2005-Jun
2005-Apr
2005-Mar
2005-Feb
2005-Jan
2004-Dec
2004-Nov
2004-Oct
2004-Sep
2004-Jun
2004-May
2004-Apr
2004-Mar
2004-Feb
2004-Jan


Calendar

< March 2006 >
SuMoTuWeThFrSa
    1 2 3 4
5 6 7 8 91011
12131415161718
19202122232425
262728293031 

Sat, 11 Mar 2006

on autopackage

Mike Hearn's 'Linux Problems' page has some interesting assertions on how to 'fix' Linux and make it 'enterprise-supportable' (which seem to boil down to: distributions suck, so avoid them; Python sucks, so avoid it; C++ sucks, so avoid that too; glibc, gcc and headers suck, so they need fixing; shared libraries, too, are hard for us, so we'd like other people to avoid dealing with them because autopackage is king).

The Debian bit is just flat-out wrong:
  • Debians dependency scanner is broken anyway, as there's no way to tell what version of a library is actually needed. Only the developers know that. It works around that problem by assuming that the binary requires whatever version it was built against (which as we see elsewhere may be true or may not be).

  • Cute, but no. Packagers can specify in shlibs files, the last ABI break. So if your library adds a new interface in 2.1.3-1, then you can put:
    libfoo 1 libfoo1 (>= 2.1.3-1)
    in your shlibs file, and wham, anything built against libfoo now gets that dependency. Of course, if the downstream packages are really ninjastupid, they can hardcode in their library deps.

  • Why should the convenience of Debian packagers, who number in the low 2s, outweigh the convenience of people who download autopackaged binaries from the website, who number in the high 200s/day?

  • Actually, last I checked, there were close on 1000 registered Debian developers, who had gone through the long process. I don't know how long the New Maintainer queue is (except: really long). There are millions and millions of users of Debian and its derivatives (Ubuntu, Knoppix, Maemo, et al). If you're going to be a condescending twat, could you at least please try to be accurate, instead of picking on Debian for being insignificant compared to your hundreds of downloads per day?
    [12:41 | /tech | # | law - all breakage mix | home ]