I'd like to have a sight over balsa (e-mail client) package. It is not on gslapt's repositories nor in sbopkg ones.
I pick it from its developer page (https://pawsa.fedorapeople.org/balsa/) which is in the balsa-xxxx.tar.xz format.
I thought that .tar.xz and .txz where the same format. I changed .tar.xz termination to txz, but it seems that I was wrong.
Launching from console #installpkg balsa-2.6.4.txz does not run.
Therefore my question: are tar.xz and txz the same?
Are tar.xz and txz the same?
Re: Are tar.xz and txz the same?
All right. Good question. It deserves a new FAQ page:
https://docs.salixos.org/faq/install-txz-found-online/
https://docs.salixos.org/faq/install-txz-found-online/
Re: Are tar.xz and txz the same?
Here's a package for Salix 15 that I built from a Slackbuild scrip for current that I got from https://slackware.pkgs.org/current/slac ... f.txz.html.
Balsa 2.6.4 - https://people.salixos.org/laprjns/balsa/
I think it works, but I couldn't set up my email account.
Balsa 2.6.4 - https://people.salixos.org/laprjns/balsa/
I think it works, but I couldn't set up my email account.
“The past was erased, the erasure was forgotten, the lie became the truth.”
― George Orwell, 1984
― George Orwell, 1984
- Van_Vinkle
- Donor
- Posts: 175
- Joined: 25. Oct 2012, 17:39
Re: Are tar.xz and txz the same?
Well, this blog entry left me disoriented.gapan wrote: ↑12. Nov 2024, 07:25 All right. Good question. It deserves a new FAQ page:
https://docs.salixos.org/faq/install-txz-found-online/
Then main reason for to use Slackware, (well, Salix because I am a little lazy ) after some years using a Debian's derivative is, in theory, the ease of compiling programs. In these years I've compiled four o five programs with success.
I am aware of issues with dependencies. This problem can be solved reading carefully the developer's instructions and doing previous installation of them.
As far as it concerns balsa email-client, I've found compiled .rpm packages. Can I use it (previously passed into rpm2tgz)?
Re: Are tar.xz and txz the same?
Why?
Sure. But that's not what you were asking about. You may find a .txz file that is indeed a package and you may try to install it. It will get installed and the software might work, or not. But you may also find a .txz file that is not a package, but merely a source tarball. Of course you can uncompress it, compile the software and install the software after you do that, you may even create a package from it. But you can't install the source tarball directly.Van_Vinkle wrote: ↑13. Nov 2024, 12:19 Then main reason for to use Slackware, (well, Salix because I am a little lazy ) after some years using a Debian's derivative is, in theory, the ease of compiling programs. In these years I've compiled four o five programs with success.
You may, but it is highly unlikely to work.Van_Vinkle wrote: ↑13. Nov 2024, 12:19 I am aware of issues with dependencies. This problem can be solved reading carefully the developer's instructions and doing previous installation of them.
As far as it concerns balsa email-client, I've found compiled .rpm packages. Can I use it (previously passed into rpm2tgz)?
Look at the post from laprjns above to find an actual package that you can install.
- Van_Vinkle
- Donor
- Posts: 175
- Joined: 25. Oct 2012, 17:39
Re: Are tar.xz and txz the same?
First, a big thanks to laprjns for his interest. I have not tried to install his balsa package because I suspect that it may break my system. The set of current's dependencies is, I think, very different from Slackware/Salix 15.
I did an investigation over others balsa packages like .rpm and .deb (it is easy to find them), but I threw in the towel, because the list of dependencies is enormous and almost none is in our repositories, probably due to balsa is a Gnome package and Slackware and Gnome are not good friends.
I installed a balsa.deb package in another old laptop, and I liked its look and its ease to configure.
I've abandoned my intention of getting balsa-mail client in my main computer. Bad luk.
I did an investigation over others balsa packages like .rpm and .deb (it is easy to find them), but I threw in the towel, because the list of dependencies is enormous and almost none is in our repositories, probably due to balsa is a Gnome package and Slackware and Gnome are not good friends.
I installed a balsa.deb package in another old laptop, and I liked its look and its ease to configure.
I've abandoned my intention of getting balsa-mail client in my main computer. Bad luk.
Re: Are tar.xz and txz the same?
You misunderstood laprjns's post. The Slackbuild was for current, the package he built with it is for 15.0. In fact I just tried it and it works. The complete list of dependencies is:
Everything is in the repos and you already have most of them installed anyway. In my laptop I only needed to install gspell.
Code: Select all
aaa_libraries
aspell
at-spi2-atk
at-spi2-core
atk
brotli
bzip2
cairo
cyrus-sasl
db48
dbus
e2fsprogs
elfutils
elogind
enchant
eudev
expat
fontconfig
freetype
fribidi
gcc
gcc-g++
gcr
gdk-pixbuf2
glib2
gmime
gmp
gnutls
gpgme
graphite2
gspell
gst-plugins-base
gstreamer
gtk+3
harfbuzz
hyphen
icu4c
keyutils
krb5
lcms2
libICE
libSM
libX11
libXau
libXcomposite
libXcursor
libXdamage
libXdmcp
libXext
libXfixes
libXi
libXinerama
libXrandr
libXrender
libXt
libassuan
libcap
libdrm
libepoxy
libevdev
libffi
libgcrypt
libglvnd
libgpg-error
libgudev
libical
libidn2
libjpeg-turbo
libmanette
libnotify
libnsl
libpng
libpsl
libseccomp
libsecret
libsoup
libtasn1
libtirpc
libunistring
libunwind
libwebp
libwpe
libxcb
libxkbcommon
libxml2
libxslt
mesa
nettle
openjpeg
openssl
orc
p11-kit
pango
pcre
pixman
sqlite
util-linux
wayland
webkit2gtk
woff2
wpebackend-fdo
xz
zlib
zstd
- Van_Vinkle
- Donor
- Posts: 175
- Joined: 25. Oct 2012, 17:39
Re: Are tar.xz and txz the same?
You were right. Installing previously gspell and then laprjns' balsa package, all was OK.
Now I'm comparing it with claws for decide which e-mail client I shall use.
Thank you very much to you and laprjns.
Now I'm comparing it with claws for decide which e-mail client I shall use.
Thank you very much to you and laprjns.