I would not do such a black and white assertion. There has been important discussions about the pertinence of slackware for porteus compared to other distributions in the last year (I cannot put the finger on it, but maybe someone else will). Though, it is good to have feedback from an external eye, so thanks for you input.
Here are some comments on the issue that you point out to bring some shades of grey. Porteus is a extremely downsized version of slackware. This is an advantage, but this is a problem too. It works almost perfectly with the modules that come with it stock (and after a few months from this 3.1 version release, it will work perfectly no doubt, we have very proficient developpers ).
There is more work involved sometimes when you want additional packages, but usm or usmgui, and other sources of packages like pkgs.org slackware, will provide an additional array of perfectly working packages without much more work. In addition, very often people forget about the capacity of usm to build on slack.builds with the sbo instructions:
Code: Select all
usm sbo -b
There are additional packages that will ask for more dependencies. Here you will need more work. In this case, you have to average linux proficient to be able to build these packages.
Have a look at the work of neko, bogomips, stifiling, vicktornova, saintless and fredx181 in development and porteus derivatives.