I last used Slack at 3.2, so I *used* to have some idea as to how to do things.
I'm tired of Red Hat for one overriding reason- the RPM-based deal is both great and awful.
It's great for speed and ease of use. But it isn't working for me as I have a machine up long-term.
In a real system, you need to apply security patches. You might need an app that isn't built into RPM. In short, you need to be able to use the old "compile in situ" and "make install" methods. As I have found, you rapidly have your package management system (whatever that may be) with no knowledge of the actual installed system.
If pkgtool could solve this, I'd gladly use Slack again.
What would be really cool? If you could analyse what "make install" was doing, and build a Slack "package" from that, then use that "package" to do the install. You could install whatever, right from source, and always have the package management system in sync with the live system.
How can I dig deeper into pkgtool operation? I'm happy to look at docs.