tar2xzm

[Ed_P]

I have downloaded a tar.xz file, extracted the .tar file but find I have no way to convert it to a .xzm file!!

Its a Zoom file to run a Zoom Client on Linux.

Suggestions?

Extract the .tar files to a directory then dir2xzm it to a xzm file. I'll let you know if that works.

[ncmprhnsbl]

this : bundle - Zoom for Porteus 5.0rc1 no good for you?

Extract the .tar files to a directory then dir2xzm it to a xzm file. I'll let you know if that works.

a bit more than that:
#mkdir -p zoom/{opt,usr/{bin,share/applications}}
put the extracted zoom folder in zoom/opt
create a link(zoom) in zoom/bin to /opt/zoom/zoom.sh (ln -s /opt/zoom/zoom.sh zoom/usr/bin/zoom)
create a zoom.desktop(blah, blah, Exec=zoom, etc) and put it in zoom/usr/share/applications
then dir2xzm zoom
you may also need: xcb-util-image and xcb-util-keysyms (running zoom.sh in a terminal will tell you about missing libs)

[Ed_P]

Thank you ncmp. At the time that was posted I had no interest in Zoom but now...

I tried the Menu > Admin > bundles approach and both files ended with Checksum Mismatch windows. And neither was named zoom.

Added in 1 hour 38 minutes 20 seconds:
Just noticed, the link you gave is for the 5.0 test system. I use the 4.0 system. You think the test system's Zoom would work in 4.0? Do you have the script you used to create the test system's module? Could I borrow it to try it with the 4.0 system?

Added in 10 minutes 29 seconds:
Maybe...

I downloaded the test system's module and activated it.

Code: Select all

guest@porteus:~$ zoom
ZoomLauncher started.
Zoom not exist at current directory - /home/guest
Zoom path is: /opt/zoom
cmd line: 
$HOME = /home/guest 
Can't load/home/guest/.config/zoomus.conf
export SSB_HOME=/home/guest/.zoom; export QSG_INFO=1; export LD_LIBRARY_PATH=/opt/zoom; /opt/zoom/zoom "" 
zoom started.
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-guest'
[CZPClientLogMgr::LogClientEnvironment] [MacAddr: AC:2B:6E:60:1D:F5][client: Linux][OS: Porteus 4.0][Hardware: CPU Core:2 Frenquency:2.3 G Memory size:3813MB CPU Brand:Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz GPU Brand:][Req ID: ]
Linux Client Version is 2.8.252201.0616
QSG_RENDER_LOOP is 
XDG_CURRENT_DESKTOP = X-Cinnamon;   GDMSESSION = 
Graphics Card Info:: 
Zoom package arch is 64bit, runing OS arch is x86_64
AppIconMgr::systemDesktopName log Desktop Name:  
qt.scenegraph.general: QSG: basic render loop
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: texture atlas dimensions: 1024x512
qt.scenegraph.general: R/G/B/A Buffers:    8 8 8 8
qt.scenegraph.general: Depth Buffer:       24
qt.scenegraph.general: Stencil Buffer:     8
qt.scenegraph.general: Samples:            -1
qt.scenegraph.general: GL_VENDOR:          Intel Open Source Technology Center
qt.scenegraph.general: GL_RENDERER:        Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) 
qt.scenegraph.general: GL_VERSION:         3.0 Mesa 18.0.0
qt.scenegraph.general: GL_EXTENSIONS:      GL_EXT_texture_shared_exponent GL_ARB_shader_ballot GL_ARB_uniform_buffer_object GL_ARB_shading_language_100 GL_ARB_shader_image_size GL_ARB_window_pos GL_ARB_shading_language_packing GL_ARB_transp

...

ARB_vertex_array_object GL_KHR_robustness GL_AMD_shader_trinary_minmax GL_ARB_half_float_pixel GL_ARB_occlusion_query2 GL_ARB_shader_storage_buffer_object GL_ARB_texture_non_power_of_two
qt.scenegraph.general: Max Texture Size:  16384
qt.scenegraph.general: Debug context:     false
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument

But I have a Zoom GUI window so it may work. We may get to see the family at Easter.

Thank you ncmp.

[otan]

Was under the impression that tar.xz was txz, in which case one could rename it to txz and use txz2xzm.

[ncmprhnsbl]

Was under the impression that tar.xz was txz, in which case one could rename it to txz and use txz2xzm.

generally not, since while txz is technically a tar.xz, it's a slackware package, which is a very particular tar.xz archive in it's structure(fakeroot + install dir).
whereas random tar.xz archives from the web, even though they may contain precompiled binaries, most likely lack the required file structure to convert to a module in the same way a slackware package does.
best approach is to extract them and see what's there.. (as you would with tar.gz, tar.bz2, zip, etc...)