This same thing I have seen with Slax; It had new build scripts which built new modules according to his requirements. The same concepts can be "copied over" and the server can update the modules *.sb -> slax module, or *.xzm which we have been using. There is too much replication going on and packages from here and from there. There is no idiot proof way of doing this! There is too much work to be done! In slackware-current there is new gcc 7.x, new packages, stable kernel 4.9.30 or higher. Slackware is a great base, slackware live by alienbob has great many packages, but it has more than what most people need or want. The bigger question should be how to accomplish this without cutting off the contributors which have always helped, the main developers brokenman and fanthom, blaze, wread, Bogo*, etc if I forget a name please forgive me. There are some folks which have left to other places. Francois which has been loyal and helps in documentation, testing. How can this be done without losing some talented folks which help the distro. Falcony you have contributed to both slax and porteus, with packages and a mirror. Slackware plain comes with no package manager that takes care of deps, but it has installpkg, removepkg clean-system, etc.Falcony wrote: Porteus needs policy for package contributes to OFFICIAL repository of packages(ftp, git) - stable and testing branches.
And maintainers of packages - OFFICLAL ones for each package - how care, test and upload its to OFFICIAL repository.
How organize this process and grant permission for conributors - tha's the right deal.
I would have to conclude that whatever solution or determination is made, some folks will not be happy.
You can please the people some of the time, but not always.