Re: Cycle de développement

Je ne suis de loin pas spécialiste, mais les branches backports genre celle de debian ne repondent-elles pas à ce que tu dis?

Si en partie. Il est toujours difficile de choisir de lier différemment ses logiciels. Par contre, slackware et ses slackbuilds répondent parfaitement à ça :)

One of the frequent criticisms of Slackware is the lack of official packages available. While the official package set provides a good, stable, and flexible operating system (and is quite adequate for many individuals), the fact remains that many users want/need quite a few additional applications in order for it to meet their needs. There are a few well-known third party package repositories, but many users justifiably do not want to install untrusted packages on their systems. For those users, the traditional solution has been to download the source code for desired applications and compile them manually. This works, but introduces another set of problems associated with managing those applications; version updates and such require more of the admin's time than precompiled packages, and lack of notes will often mean that the admin forgot which configure flags were used earlier (as well as any other special issues encountered).

In our opinion, the best solution to this problem is for the admin to automate the compile process using a SlackBuild script.