[Pkg-ltsp-devel] dropping support for most architectures

vagrant at freegeek.org vagrant at freegeek.org
Sun Feb 10 21:33:11 UTC 2008


so, i'm seriously considering dropping support for architectures other
than i386, powerpc and amd64 for ltsp.

i do most of my testing on i386.

i can try to test on powerpc occasionally.

i don't have amd64 systems to test on, but i'm not so worried about
amd64 anyways.

i've tried getting sparc to work, but a bug in klibc-utils has always
blocked the network booting from working: http://bugs.debian.org/444087

as far as all the other architectures... can we just drop them?

our network booting code only handles powerpc, i386 and amd64, and
there's untested code for sparc and alpha.

does it amount to simply editing debian/control and specifying 

architecture: i386 powerpc amd64

or is there something more we'll have to do?

would it be an option to drop support for ltspfs and ldm as well? or do
we need a better excuse than ltsp is poorly supported and these two
things are largely related to ltsp?

currently the mips and mipsel buildd's are preventing ltsp and ldm from
migrating to testing. i was hoping to get a new ldm upload as soon as
they hit testing, but now i'm thinking i'll just upload to unstable.

testing is in a bad state right now, because ltspfs and the version of
ldm in testing are incompatible, so ltsp-client installs sdm-terminal,
which basically breaks localdev and sound support (without a fair amount
of manual hacking)...

soon, i'll probably drop sdm-terminal as an allowable dependency for
ltsp-client, and only make it a suggests of ltsp-client-core, as the
next upload of ldm will have pretty much all the features that sdm has,
and more.

live well,
  vagrant



More information about the Pkg-ltsp-devel mailing list