jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
<beerman> jaeger: basically there is way too much movement in regards general python packaging
<beerman> when you look at pyproject.toml or whatever the file is called it will tell you which build system it uses, and lucky for you, it just wants build/wheel/install iirc
<beerman> i dunno if thats wrong per se but yeah
<beerman> jsonschema is obviously hackish :P
farkuhar has left #crux-devel [escaping from the python packaging madness]
<jaeger> seems like both of those examples use setuptools.build_meta
<jaeger> So what's the "preferred" way for packagers to use that?
<beerman> that way, I suppose
<beerman> mind that i am not 100% sure because I am much more all over the place, sadly..
<beerman> that you need to chmod the binary must be an oversight upstream
<jaeger> yeah, the chmod seems weird
<jaeger> does this build for you without footprint mismatches? http://ix.io/3PZX
<beerman> rebuilding in a container..
<beerman> seems ok for me
<jaeger> ok, thanks
ivandi has quit [Quit: WeeChat 3.4]
ivandi has joined #crux-devel
SiFuh_ has quit [Ping timeout: 240 seconds]
SiFuh has joined #crux-devel
<beerman> jaeger: http://sprunge.us/2nBWCd using pep 517 build and pip to install the wheel doesn't seem to need the chmod workaround
farkuhar has joined #crux-devel
groovy2shoes has quit [Ping timeout: 240 seconds]
groovy2shoes has joined #crux-devel
ivandi has quit [Quit: WeeChat 3.4]
ivandi has joined #crux-devel
darfo has quit [Remote host closed the connection]