[PACKAGING] Fix FPM-based installation location

HorlogeSkynet commented 4 years ago

See #59. Multiple RPMs will now be generated, named as : archey4-4.Y.Z-R.py3.V.noarch.rpm (with V the second segment of a Python version). Users will HAVE TO pick the correct package according to their Python 3 environment.

How has this been tested ?

Docker containers for each affected distribution.

Types of changes :

[X] Bug fix (non-breaking change which fixes an issue)
[ ] Typo / style fix (non-breaking change which improves readability)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist :

[ ] [IF NEEDED] I have updated the README.md file accordingly ;
[ ] [IF NEEDED] I have updated the test cases (which pass) accordingly ;
[X] My changes looks good ;
[X] I agree that my code may be modified in the future ;
[ ] My code follows the code style of this project (PEP8).

brilliant116 commented 4 years ago

The solution may be fine.

HorlogeSkynet commented 4 years ago

Thanks for your fast reply, let's get this merged then. I hope to draft a v4.7.1 next week, new packages will be generated with this method at the moment.

Bye :wave:

HorlogeSkynet / archey4