last time I checked, the Salix repo was quite huge and I think that there will be a lot of redundancy with MLED packages. So I guess the number can be dramatically reduced.
I already stated long time ago that I find it an mistake that MELD did not choose Salix as it's base, since the project was simply to huge.
And Salix offers some tools out of the box MLED needed, graphical package manager, update applet, ...
I also think that Salix has an interesting style to build packages, but I need to revisit this since it is a while I checked.
But I think I remember that it is possible to get rid of a lot of the usual boilerplate script stuff Slackware buildscripts contain, so packaging on Salix should be much more fun.

1 members found this post helpful.

I had considered that for some time. Salix is excellent, and George Vlahavas (gapan) is a nice and competent guy. In the end I decided against it, because I wanted something closer to Slackware than to Salix, and a number of my packages were built differently and conflicted with those in the Salix repos.

Niki

He is, though. CentOS is not officially blessed by Bob.

3 members found this post helpful.

Off topic, but Salix is about as close to Slackware that you can get without installing Slackware. So it could have also have been feasible to join the Salix team and then create your support company from Salix/Slackware (back then of course, too late now that you already switched to CentOS, which is perfectly fine as well)

Curious, how did your clients handle the news? Or did they not care as long as everything works?

1 members found this post helpful.

Be well my friend. So long thanks for all the fish

1 members found this post helpful.