Zeronet: Libs seem out-of-date according to this post (link in desc)

Created on 5 Apr 2017  路  3Comments  路  Source: HelloZeroNet/ZeroNet

https://news.ycombinator.com/item?id=14041596
Maybe we should update them and not bundle them directly into git?

Most helpful comment

Using pip for dependencies would make the portable/exe/.app version really hard

Not really.

Appveyor supplies CI for Windows systems, and can automatically bundle you an *.exe at each step, and is free for open source projects.

Travis CI Enterprise supplies both Macs and Linux machines for you to automatically bundle with, and is free for open source projects.

It's a case of writing two files:

  • .travis.yml
  • appveyor.yml

Then, linking the repository to accounts with Appveyor and Travis.

They'll test your test suite at each commit, and can build your bundles for you.

There's no reason not to use pip.

And if you continue not to use a package manager of any sort, you will continue to run into these issues. Outdated libraries, and insecure libraries.

(On that note, I'm afraid you need to replace PyElliptic. It's no longer receiving updates. Maybe use the canonical OpenSSL library for Python: pyOpenSSL)

All 3 comments

Thanks for the heads-up I will update the libs. Using pip for dependencies would make the portable/exe/.app version really hard, that's why I decided to include them.

Using pip for dependencies would make the portable/exe/.app version really hard

Not really.

Appveyor supplies CI for Windows systems, and can automatically bundle you an *.exe at each step, and is free for open source projects.

Travis CI Enterprise supplies both Macs and Linux machines for you to automatically bundle with, and is free for open source projects.

It's a case of writing two files:

  • .travis.yml
  • appveyor.yml

Then, linking the repository to accounts with Appveyor and Travis.

They'll test your test suite at each commit, and can build your bundles for you.

There's no reason not to use pip.

And if you continue not to use a package manager of any sort, you will continue to run into these issues. Outdated libraries, and insecure libraries.

(On that note, I'm afraid you need to replace PyElliptic. It's no longer receiving updates. Maybe use the canonical OpenSSL library for Python: pyOpenSSL)

Thanks for reporting, I have updated all of the libs to the latest version.

The PyElliptic still has some updates via the BitMessage project: https://github.com/Bitmessage/PyBitmessage/tree/master/src/pyelliptic

The pyOpenSSL looks nice, but it has more dependencies and not pure-python, so I would stick with pyelliptic if possible.

I keep it open as I want to add automated way to update the libs to avoid the same problems in the future.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

BenMcLean picture BenMcLean  路  3Comments

clamever picture clamever  路  4Comments

wigy-opensource-developer picture wigy-opensource-developer  路  4Comments

iShift picture iShift  路  3Comments

DaniellMesquita picture DaniellMesquita  路  3Comments