I do understand the philosophy behind Slackware and Salix. That's exactly why I am approaching Salix.
To be clear, I am not requesting to update the repositories. Moreover, if for some reason I would want to use updated partitioning tools, there are enough alternatives so that I wouldn't even need to think about building some updated package by myself
I would say that my question was more about understanding how the Slackware / Salix philosophy would apply in practice to these type of (important) tools, specially when bug fixes might be crucial.
Let me put it this way. A few years ago, cfdisk (util-linux) was version < 2.19. At some point it was updated to v2.19 in Slackware. I am wondering what triggered that update (or any update of cfdisk in Slackware before that). For example, is it just the next beta cycle? Or, if it is something else, then what triggered that update, but not to have available the new updates to util-linux in the repositories of Slackware. After all, we are not talking about "some random package".
I don't want to get OT, but I’d like to give a different example so to illustrate the goal of my question. mkisofs of cdr-tools is currently in alpha development. Currently there is alpha 7 available, yet Slackware has alpha 2 available, and of course there is the (previous/current) stable version. Then, what triggered the availability of alpha 2, and why not to update to alpha 7
This OT example is very different from the OP, but it has in common, at least in part, the same kind of wondering behind the original questioning.
OTOH, if all this happens to be just about available time of one person only (which I'm not saying that's the case; I just don't know), then the real reasons are not just philosophy or stability
I hope I am making more sense about the intention of these questions.