Page 1 of 1

Installing tar.xz Packages Correctly

Posted: 07 Sep 2016, 20:05
by FURRY_NOVA
When I double-click a tar.xz file I've downloaded, there are no applications to open it. However, on Porteus 3.1, there was Xarchiver pre-installed. Even though the application wasn't assigned to open them, I managed to extract the contents with Xarchiver into a folder and run them in that folder as an application in Documents. But later I noticed Whisker menu assigned a icon link for it like it's supposed to run like a module.

I imagine there's a correct Porteus way of installing them. Making them xzm modules and placing them in module folders but, how would I do that? :unknown:

Re: Installing tar.xz Packages Correctly

Posted: 07 Sep 2016, 20:21
by Bogomips
From where has the file been downloaded? Normal Slackware are mostly .txz with a few being .tgz.

Re: Installing tar.xz Packages Correctly

Posted: 07 Sep 2016, 20:34
by FURRY_NOVA
I got it from here: https://desktop.telegram.org I know there's a module on forums and USM but I thought getting it from their site directly would be better and secure.

I browsed around before and saw they done the same with VLC Media Player on another site with tar.xz but because Porteus uses a different module or something system, I thought it best to ask about it.

Re: Installing tar.xz Packages Correctly

Posted: 08 Sep 2016, 02:20
by francois
Just right click on it and uncompressed the file and see what you get. :twisted:

Re: Installing tar.xz Packages Correctly

Posted: 08 Sep 2016, 03:34
by fullmoonremix
Solution...

Rename /~/*.tar.xz as /~/*.txz then convert w/ USM to /~/*.xzm

Posted by 73.112.17.112 via http://webwarper.net
This is added while posting a message to avoid misusing the service

Re: Installing tar.xz Packages Correctly

Posted: 08 Sep 2016, 03:57
by FURRY_NOVA
So tar.xz are actually longer name of txz, just been browsing around. I've converted it successfully but doesn't add to Whisker menu. So, I'm guessing it supposed to work as portable executables.

Thanks for you helps guys.

Re: Installing tar.xz Packages Correctly

Posted: 08 Sep 2016, 08:39
by fullmoonremix
I'm sorry... I forgot to mention that "tar.xz" is for the Arch Linux package system.

Posted by 73.112.19.101 via http://webwarper.net
This is added while posting a message to avoid misusing the service

Re: Installing tar.xz Packages Correctly

Posted: 08 Sep 2016, 08:47
by Bogomips
Made script xz2txz.sh which will make Slackware compliant package: http://forum.porteus.org/viewtopic.php? ... 577#p33210. Might get funny name, name fixing next on agenda. But suitable then for conversion txz2xzm. Might help to get it on the menu. Let us know if it works.

Re: Installing tar.xz Packages Correctly

Posted: 08 Sep 2016, 17:48
by FURRY_NOVA
Bogomips wrote:Made script xz2txz.sh which will make Slackware compliant package: http://forum.porteus.org/viewtopic.php? ... 577#p33210. Might get funny name, name fixing next on agenda. But suitable then for conversion txz2xzm. Might help to get it on the menu. Let us know if it works.
Well, I've tried it out. I found if the sh file and tar.xz package are in a folder with spaces. It causes a script error. Desktop/New Folder/ for example when run.

After renaming the folder to folder, the script worked making a txz and I converted it to xzm but the Whisker menu didn't contain the link after activating it.

Also some odd behavior started happening after testing it in Always Fresh mode. When I rebooted to GUI, saw some error that it can't find "all" and "allfiles" types in sbin or something. When it started, I couldn't get Porteus to access WiFi since even checkbox was disabled in NetworkManager Applet. Even Network Connections wouldn't open in Whisker. Deleting Kate and like 20 packages it wanted made it work but didn't cause this before.

These are the contents of the tar.xz package just for noting.
- Telegram (executable)
- Updater (executable)

Re: Installing tar.xz Packages Correctly

Posted: 08 Sep 2016, 19:32
by Bogomips
Well, it looks like there are unsatisfied dependencies and incompatibilities. So the guiding principle is that if it can be got with usm then gettting it means Slackware packagers have already ironed out the incompatibilities, after which usm will fix up the dependencies.

It's only if one absolutely has to have the very later versions that one should spend time in sorting out xz or deb or rpm packages.