brent I don't think Serpent is using eopkg at all.
Serpent will use the moss package manager. Many of the same ideas that originally went into eopkg (and its underlying infrastructure) are also present in the Serpent tools. It should be pretty familiar to anyone who's been around Solus for a while.
A fair question to ask then is "if the underlying ideas are the same, why develop new tools at all?" To which I would reply:
- The old tools carry a tremendous amount of tech debt, and that causes a lot of headaches
- Not all of the ideas are the same. Serpent tools have features that no one had dreamed of when eopkg was being designed.
My understanding is that Serpent will be the upstream to Solus, meaning that all the cool new stuff will come to serpent first, be tested, tweaked, and validated there, and then pulled into Solus once it's ready for general consumption. Sort of like how we do our unstable and stable repositories today.