search

viper-framework / viper

Binary analysis and management framework
Other
1.54k stars 351 forks source link

Create PyPi package and new rolling release model #696

Closed botherder closed 5 years ago

botherder commented 6 years ago

Releasing version of Viper has been an embarrassingly slow and painful process. At this point versioning isn't even really a useful thing.

In order to revive Viper in a more usable software, I think it is necessary that we invest some time in making a PyPi package happen, which could also allow for a proper updating mechanism and that would allow us to remove the viper-update utility which is outdated and half-broken.

frennkie commented 6 years ago

I started looking into this some time ago.. (e.g. #614) but it's not trivial.. But I think it's definitely worth the effort.

botherder commented 6 years ago

As a very first step we need to unify the installation process. Clearly the current setup.py has some issues, as not all dependencies are installed. Maybe I can for the moment change Makefile to include all the steps used by @frennkie here https://github.com/viper-framework/viper/issues/665#issuecomment-414399374 which seem to work fine. Thoughts? @Rafiot?

Generally speaking though, I think we should remove the Makefile and just push on setting up the PyPi. @frennkie I would suggest you create a dedicated branch on this repository (you should have commit rights now) and we work on that there and only merge in master once it's actually working.

botherder commented 6 years ago

With #702 and following commits the pip-based installation process seems to be working. PyPi packages will be uploaded when releases are made.