Quote:
Originally Posted by roger64
[B]Even now, I can launch Sigil only with a script giving him every time the location of the Qt5 library (this idea coming from Diap Dealer).
I hope I am alone facing these hurdles, because the number of Linux users may drop dramatically if this install is not made clearer.
|
Glad you got it working.
The problem is... it's not really an install, it's a
build. As such, it will never be completely easy/clear. That's just the nature of custom compilation—it's not for the "casual" Linux user.
I agree with you—to some extent—about possibly losing Linux users. But at the same time... I also recognize the need for the Sigil devs to wash their hands of any Linux "install program." In the Linux tradition, it's the duty of repository maintainers to provide a simple binary installation package (ensuring all necessary dependencies) for open-source software and not the software developers.
Unfortunately, this means that the easy/clear installations of your favorite open-source software will never be the most up to date versions. There's a lag. If you want the cutting edge versions, there will always be hoops to jump through in setting up a proper build environment.
If you want more recent versions of Sigil to be a part of your flavor of Linux's repositories... then you need to hound the maintainers of those repositories (although in this case, even if a repo maintainer were willing to take up the cause, Sigil 7's Qt 5 dependency is going to cause some issues, since I don't believe there's any binary Qt 5 packages in any of the standard repos just yet).
Some knowledgeable users might be able to work up some custom debian|rpm packages that included only the necessary Qt libs and a custom launch script if they were feeling generous. Might make it a
bit easier on the non-technical Linux user.
