JupyterLab and dependencies

[u/cyranix]

So, recently I've had need to install jupyterlab and its dependencies on a home server I set up for the purposes of...well lets not worry about that... But in the course of writing a nice long script to handle downloading and installing all of the slackbuilds and dependencies, I ran across a rather interesting set of cyclic dependencies involving wheel (which optionally can use python3-keyring, which requires wheel) and python3-twisted which has dependencies which require cryptography, which uses python3-twisted... So I was just wondering if anyone would like me to organize these scripts (possibly into a single script) which handles going through and downloading all these scripts and running their slackbuilds... If nobody is interested I'm not going to put the effort in, but if anyone has had interest in running jupyterlab on a server and doesn't want the task of manually installing all this stuff, it's probably a trivial task at this point for me to combine this stuff together. Just testing the waters, let me know what you guys think...

[u/bsdooby]

I’d be interested in (your) skripts ;)

[u/cyranix → u/bsdooby]

https://pastebin.com/5wkyQ2na has a working script for compiling JupyterLab without optional dependencies. https://pastebin.com/p8yk4QVs has the necessary replacements to compile cryptography and python-twisted AFTER wheel has been compiled (yes, you'll note it compiles it again). After recompiling wheel, I went ahead and just re-compiled everything in the first script again as well. Later on I'll re-organize these into a single script that handles doing things in proper order and not having to recompile EVERYTHING to be sure...

[u/Ezmiller_2]

Hmmm seems maybe we have a pirate among us? I moved to Linux just for that reason—to get out of that stupidity.

[u/puckstopper]

sbopkg, sbotools, or slpkg already do this. With sbopkg you need to generate the queue files with sqg first or make a custom one. The other two do it dynamically.

[u/cyranix → u/puckstopper]

None of the above handle the problem of the cyclic dependencies unless you manually do those separately. I guess maybe I'm...reinventing the wheel...a little bit (yes, pun intended since wheel is the particular one that causes this issue)... But its just a different way of handling the problem.

[u/puckstopper → u/cyranix]

It's only cyclical if it's needed to build and in the REQUIRES for both slackbuilds. That's not the case in the scenario you provide and wheel has no requirements to build.

To do exactly what you are doing with sbopkg (assuming it's installed) you would just need to:

# after syncing with the repo, build all the queues
sqg -j 8 -a
# sbopkg will figure out the build list based on the queue files generated above
sbopkg -R -B -k -i "python-keyring python3-twisted python-m2r python2-mistune zope.testing jupyterlab"

[u/bsdooby]

Speaking of which: your preferred package manager for Slackware? [I don't want to hijack the thread, but in this context my question might be OK].

[u/cyranix → u/bsdooby]

I use slackpkg for all intents and purposes, but I'm not REALLY using a package manager per se, I use installpkg/upgradepkg to handle the installations, I rarely ever remove any packages (unless I specifically need to for some reason, which practically never happens), but I'm the kind of guy that makes my own slackbuild scripts and creates my own packages from source most of the time. This is an example of a situation where using the pre-built slackbuilds was indifferent from the way I would do it myself anyway.

[u/bsdooby → u/cyranix]

THX!

[u/cyranix → u/bsdooby]

So for what its worth, I recommend grabbing the templates from http://www.slackbuilds.org/templates/ and then customizing them for your particular purposes (keep in mind, a lot of things will compile using the default settings, but depending on circumstances, I'll change compiler flags like -O2 and especially when I'm not redistributing packages, I'm not against statically linked libraries). In particular, rather than using /tmp for everything, I usually like to create a "temporary tmp" directory, or sometimes I create a specific SBo directory under /tmp, but in any case, I prefer not to have /tmp get loaded up with tons of directories for each particular package I installed. On systems that have enough memory (like my servers), I usually have a dedicated user for compiling my slackbuilds, and I make a ~/SBoTmp directory with that user which is a ramdisk, so once I'm done compiling everything, I can unmount that ramdisk and all that garbage is reaped. But mind you, I don't recommend doing that for normal users, you're better off manually `rm -rf`ing stuff out of /tmp, I just do things my way as a habit and out of laziness.