bbqD wrote: ↑
Wed Apr 04, 2018 6:12 pm
Looking at Solus documentation, I thought building the application using solbuild & eopkg commands was the 'normal way' for Solus. What normal way are you referring to?
The "normal" way or the Linux way is to just compiling it without creating a distribution specific package and installing it.
Let's say you want to compile a custom version of Thunderbird (pick any program really).
You have the options:
1. compile it from source as it's stated on their page, something along the lines of `make` and `make install`. You receive a `thunderbird` binary which you can run like this: `./thunderbird`.
2. provide the Solus specific configuration (the packager file, package.yml, etc. ) and use the solbuild tools to build a `thunderbird.eopkg` package (which contains the binary program but is not runnable per se), install this package using `eopkg it thunderbird.eopkg`.
This does a lot of other stuff for you, so you can make explicit dependencies which are guaranteed etc...
Actually I have yet do to this on Solus, but that's more or less the gist of it for every/most distribution.