Package Installer vs Apt

[Member blur13]

Hi!

on antiX 19.5

I’m wondering what the difference is between installing a program using the antiX Package Installer gui and using apt in the terminal. Are both using the same repos and pulling in the same version of the programs?

What about the “cli apt-based package manager”?

thanks!

[Forum Admin dolphin_oracle]

Helpful

Up

0

::

package-installer sometimes pulls from other outside repos and sources on a case by case basis. cli-aptix also has some metapackage functions IIRC, but it sticks to the default repos, and is designed help with package management outside an X environment.

all the tools mentioned utilize the terminal libapt clients apt and/or apt-get for the actual installs, so once you get to actually installing a package, the actually install is the same as the cli tools.

[Member blur13]

Helpful

Up

0

::

Thanks for your reply dolphin_oracle! To follow up on that, what would be the reason for “package-installer sometimes pulls from other outside repos and sources on a case by case basis”? Is the package modified to better suit antiX in some way? If a package is available in the package-installer and the debian repos, should preference be given to the package-installer version? Is there a way to check what package the package-installer intends to install, and from what repo, short of actally installing it? Sorry for the question overload.

[Forum Admin dolphin_oracle]

Helpful

Up

0

::

mostly its for things that aren’t in the debian/antiX repos already. on MX we do that with things like google-chrome, teamviewer, and a few other things. I don’t remember exactly what all is in the antiX packageinstaller that isn’t pulled from the repos. each entry is defined by a *pm file under /usr/share/packageinstaller so you could look at the file to see what its going to do. If there is nothing in the “preinstall” area then its just going to pull from the repo anyway.

• This reply was modified 1 year, 2 months ago by dolphin_oracle.

[Member PPC]

Helpful

Up

0

::

@blur13 -like D.O. said… Think of Package Installer as a way to run a script that installs the particular application(s) you choose- either from the official repository or from anywhere else- that’s way you can install the latest versions of some applications (like LibreOffice and Gimp), that are not in the official “regular” Debian repository. This means that in antix you have a GUI to install several applications that either are nor available in the Debian repository or, if they are there, they are in an older version.
So, I usually look first in P.I. and if the app I want is not available thee, I use apt/synaptic, and if it’s not there either, I look for appimages/flatpaks. If I still can’t find what I want, then I fish around for a .deb file not officially supported in Debian (but that may work in Debian/antiX)
The only “problem” that antiX has, if you wish to think of it that way, is that in antiX you have no way to install applications that are available only in snap form (I only noticed one such app I needed- an android emulator),

P.

[Member calciumsodium]

Helpful

Up

0

::

dolphin_oracle wrote:

each entry is defined by a *pm file under /usr/share/packageinstaller so you could look at the file to see what its going to do

Hi,
During this past month, I have had to use packageinstaller to install wine in order to run a windows chess program that requires .net framework.

My usual way to install wine in my 64-bit system in terminal is

sudo apt install wine wine64 wine32

This works for all my windows applications except for the one windows program that requires the .net framework.

When I installed wine via packageinstaller, a wine-mono program gets installed. As I understand it, this wine-mono program allows wine to run .net framework.

When I looked under /usr/share/packageinstaller-pkglist/wine.pm file, I don’t see anything about wine-mono. It just mentions wine. The *.pm does not list which programs get installed, particularly in the case of installing wine. Is there a way to find out what list of files get installed via the packageinstaller for a particular package and also in which repo?

Thanks

[Member ModdIt]

Helpful

Up

0

::

@PPC, gave me false hopes :-).
Regarding Gimp, the available version through packet installer is 2.10.28, the latest bugfix gimp is 2.10.30,
it needs major librarys not available in Bullseye, still no sign of a backport so probably not possible.
There is a flatpack which has some weird issues.

@dolfin_oracle. thanks for more on the workings of package installer, a very useful tool.

@ calciumsodium Regarding wine, the packet installer pkg list config gives -t mx winehq-staging not the standard Bullseye version.
so there will be differences and bugfixes. I am guessing also dependencys

[Author]

Posts