in reply to Eugene

Thanks, this could be added to the documentation if you feel like writing a pull request for it. :)
I am surprised it took so long to build the rust dependency. There are also some C dependencies used by pyrofork (the telegram lib we use), so it's probably not 100% rust's fault.
I am also surprised you had to install so many py313-xxx dependencies, since you end up calling `pip`, this should take care of installing them. (but I don't know anything about netbsd, so I may be wrong)
in reply to Nicoco

@nicoco
> I am surprised it took so long to build the rust dependency. There are also some C dependencies used by pyrofork

Aha, this probably describes why I had two peaks on the graph. The first is 30 minute building of Rust dependency, which I saw in the console. And the second, lower, for 20 minutes was for some C dependency, when I was away from the console. At least, looks like so.

It was so long because I an have Intel Atom N2800 CPU and 2 Gb RAM in this machine :drgn_hyper:

Also this was a reason to preinstall some python dependencies (and dependencies of dependencies) from NetBSD packages — I tried to reduce time in pip, downloading and preparing everything :drgn_blush_giggle:

in reply to Nicoco

I recheck this and yes — pip reinstall some packages, when it need another versions, which don't match with versions from NetBSD repo. But most of the packages just reused — pip writes that "requirement already satisfied" (see the screenshot №1).

And it writes one compliant — at the end of installation, about possible system break after it was running from root user (on the screenshot №2)

P.S. As I see pip downloads only: slidgram, pyrofork, slidge, slidge-style-parser, pyaes, pymedia-pyrofork, PySocks, tgcrypto-pyrofork, python-magic, slixmpp, thumbhash, aiodns, pyasn1, pyasn1_modules, pycares.

This entry was edited (1 week ago)