Installation difficulties, shared libraries

[kemde]

Guys, this may sound like a rant, and it is to a degree :-)

You should deliver the correct versions of shared objects that your installation depends on. Your program wants zlib 1.2.9, but 1.2.7 was installed by the installer. Renaming the file and deleting the links does it.

If you install files with a superuser bit set (PixInsightUpdater), you should inform users before you do so because this is a very serious security issue ! Linux is before all a multiuser OS and such hacks are completely unnecessary, if not smelly.

Anyway, i suggest that you should allow the user to install software where she/he likes, especially in her/his home directory to avoid mingling with vital things like dev environment etc. As it is now, pixinsight must be installed in a vm or on an own pc.

Apart from that, it is the best linux program for the use case on the market.

Just sayin' ...

:-)

[Juan Conejero]

Thank you so much (well, I think )

I'll try to fix all of these incompatibility issues in the next version, especially this ugly zlib problem...

[kemde]

Thanks for the quick reply :-)

If there was a possibility to install pixinsight completely into the home directory with no need for root right for the updater, that'll be a giant leap for pc security :-) Edit: well, i am somewhat on the pedantic side here, but i think it is worth thinking over.

[Juan Conejero]

If there was a possibility to install pixinsight completely into the home directory with no need for root right

You can simply uncompress the distribution archive on your home directory, then run PixInsight.sh from the resulting PixInsight/bin subdirectory. Actually, there is no need to install the application on Linux. You can create menu and (if desired) desktop entries manually.

[kemde]

Oh, thanks, works perfectly ! Why didn't i try this right away ?

I was under the impression that the installation process was mandatory ...

Thanks again !