foxbishop I'm curious, other than the inconvenience why should I hesitate to do this method? It seems pretty robust.
As a general rule, using a package in the repository is the preferred method to install an app, for several reasons:
(1) the repository app was converted to .eopkg by a Solus team maintainer who knows what he/she/they are doing, so packaging errors, such as missed, incorrect or incompatible dependencies, are less likely in a repository package than in a roll-your-own,
(2) an eopkg in the repository is tested on an ongoing basis, so the package is less likely than a roll-your-own to screw up the installed distribution as the app and Solus change over time, and
(3) a roll-your-own .deb to .eopkg has to be self-maintained in a private repository (rather than maintained by the Solus team maintainer) on an ongoing basis, which can be a real pain if the package updates frequently (as in, say, a browser, which is the one app I package privately).
That is not to discourage you from ignoring the repository and rolling-your-own packages and maintaining a private repository. The instructions for doing so can be found in the Help Center. You'll learn a lot over time straightening things out, maintaining the package, and keeping the package in sync with changes in the Solus OS. It isn't rocket science. My view, though, is that rolling-your-own is best used only when a package is not in the repository or available as a Flatpak or Snap.