Slashdot Mirror


Custom Debian Distributions

Andreas Tille writes "When the first Custom Debian Distribution - Debian Junior - started in the beginning of 2000 we did not expect that this would perhaps lead to a new way Debian could support its end users in general. The next step forward was done in DebConf3 in Oslo when several developers who care about Custom Debian Distributions met in person and decided to work together more closely. Finally at OSWC conference in Malaga took place a workshop aiming at exactly this issue. The result of the conference was to write a paper about Custom Debian Distributions to explain to the public what we had done and what we want to do. This is an implicit call for participation for all those people inside and outside Debian who work on the same goal: Enhance the role of Debian as the missing link between upstream software developers and end users."

1 of 203 comments (clear)

  1. Re:Differences between custom and based? by GrnyS · · Score: 5, Interesting

    From the developer's perspective, by making a Custom Debian Distribution, my project, Debian Jr., can afford to focus strictly on making Debian better for children, and not have to worry about providing a whole new infrastructure that is necessary for a Debian derivative.

    From the user's perspective, they are going right to the source for support and bug reporting, rather than filtering everything through a third party. They don't need to worry about whether package foo from Debian main will work with their Debian derivative or not. And if package foo *does* break, someone is actually on the hook for fixing it, whereas with a derivative you're likely to encounter this:

    User: Package 'foo' is broken when I use it with Debian derivative 'bar'. Help!

    Derivative developer: Sorry, that's your problem. We don't maintain 'foo'.

    Debian developer: Sorry, that's your problem, I don't run 'bar', so I can't debug it.

    --
    synrg at debian dot org