Slashdot Mirror


Debian Release Mgr. Proposes Dropping Some Archs

smerdyakov writes "In this story posted by Andrew Orlowski of the Register Debian Release manager Steve Langasek has announced that support will be dropped for all but four computer architectures. Among the reasons cited for doing this are improving testing coordination, 'a more limber release process' and ultimately a ('hopefully') shorter release cyle. The main architectures to survive will be Intel x86, AMD64, PowerPC and IA-64." Actually, the story says clearly that this is only a proposal at this point, but it's definitely something to watch.

4 of 377 comments (clear)

  1. Dropping ARM??? by LWATCDR · · Score: 5, Insightful

    That might really hurt embedded developers. Seems like embedded users would be far more likely to use Deb than IA-64 users.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  2. Re:In other news... by Thud457 · · Score: 5, Insightful

    Aren't porting and actively supporting two different things?

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

  3. Re:The hell? by Anonymous Coward · · Score: 5, Insightful

    THANK THE LORD!

    Someone at Debian is finally getting a fucking clue. I've been telling stupid Debian zealots this for years... your distro is dying because everything has to move in lockstep. Take a look at the Linux kernel -- it's x86, and yet there are loads of ports which move at their own speed. Debian is a slug of a distro because it moves at the speed of the absolutely *LEAST* developed port. Split them off focus on the x86 distro... and let the other catch up or die off. Debian is smothering... and all the puffed up insane zealotry about how other platforms are supported just as well as x86 is worthless if your distro is 5 years out of date.

  4. Re:I disagree wholeheartedly. by noahm · · Score: 5, Insightful
    Interesting, I run Debian, with kde 3.4 over kernel 2.6.10 and my distro does not feel 5 years out of date.

    Sure, you run sid. You know what that means? It means that this proposal won't affect you at all. (additionally, I'm sure you run x86, along with what, 98% of all other debian users?)

    The thing is, you're the type of user who doesn't need predictable release cycles. You can get by on the bleeding edge and run software for which a new package release may be uploaded on any given day.

    A lot of Debian users are in very different positions. I, for example, run Debian in an enterprise environment, with literally hundreds of servers and workstations. woody is simply not an option in this environment. Hardware support (both kernel and user space) is dreadfully lacking, and we'd have to backport most of the software we use every day anyway. We'd end up running something so bastardized that we'd no longer see many of the benefits of running Debian at all. So we were forced to go with something more current. We chose sarge, with the understanding that we'd have to be responsible for the security of our systems, with little help from Debian. But of course, there are problems there, too. Sarge changes every day. A machine installed today may look nothing like a machine installed tomorrow. Additionally, we simply have no way of knowing when sarge will be released. The saying within Debian has always been "we'll release when it's ready", but of course, there's never a published metric for readiness, so there's simply no way of knowing when that will be.

    Basically, right now, Debian really doesn't have a good release for enterprise users. That really sucks, since IMHO Debian provides a software infrastructure that makes it really appealing for large scale deployments. I really hope this new proposal is a step toward a shorter and more predictable release cycle!

    noah

    (Debian developer, sysadmin, and user since 1997)