From Mageia wiki
Jump to: navigation, search


Drakconf multiflag.png
 Other languages
Deutsch ; English ; Español ; Français ; Nederlands ; Português (Brasil) ;
Synopsis:
O Mageia oferece uma grande variedade de software já empacotado. No entanto, não podemos ter tudo, e nem sempre as versões mais recentes.

Pode até ser que você queira alguma versão mais antiga ou instalar mais de uma versão ao mesmo tempo.

Aqui estão alguns métodos que podem ser usados.

Realmente não está no Mageia?

Primeiro, verifique se o que você procura realmente não está empacotado. Pode estar sob outro nome, então lembre-se de que os nomes dos pacotes geralmente estão todos em minúsculas. Além disso, você pode usar outro programa. Por exemplo, dependendo do ambiente de desktop que você instalou, diferentes leitores de PDF são instalados por padrão, como o Okular para o Plasma.

Aqui está uma lista de alguns dos aplicativos no Mageia.

Na interface gráfica do Gerenciamento de Software do Mageia, você também pode pesquisar por descrição. Consulte a documentação, item 3: Modo de pesquisa. Na linha de comando, você pode usar urpmq e urpmf.

Você também pode verificar usando o Banco de Dados de Aplicativos do Mageia.

Para descobrir quais programas podem ser de interesse, experimente:

Se você não encontrar o aplicativo desejado em nossos repositórios oficiais, confira também os Repositórios externos com pacotes do Mageia, e verifique se ele está disponível em um dos Formatos universais de pacotes suportados.

Se não encontrar o programa que precisa, por favor, pergunte no nosso fórum!

No repositório backport do Mageia, você pode encontrar programas da próxima versão do Mageia ou atualizações que exigem atenção especial. Consulte urpmi.addmedia.

Você também pode reempacotar um programa de outra versão do Mageia por conta própria. Veja Pacotes RPM de outra versão do Mageia abaixo.

The proprietary drivers

The proprietary drivers i.e for graphics and wifi are shipped in the non-free media. I.e. for Nvidia enable the nonfree and nonfree_update repos, and in MCC when you configure your Nvidia video card you will be asked if you want to use nouveau or the Nvidia driver.

Patent encumbered software

A lot of audio and video codecs that are restricted from free use in smaller or larger part of the world, and programs with such built in, are in the tainted repos.

Optimally you should check if you can legally use some particular package from there, depending on usage and in which part of the world you are, before installing it.

If you want to update everything installed to the versions from the tainted repos: enable both tainted and tainted_updates, on 64-bit systems also the 32-bit versions, and as root issue urpmi --auto-select

Normal package handling in Mageia

If you do not know the default package management in Mageia, please first see:

Install media in Mageia for beginners

Install and remove software for beginners

Installing and removing software

Software management

About using the command line see URPMI.

More on package management in Mageia

News from Release notes.

You may use DNF as package manager: see above link and Using DNF. It will use the same rpm database as urpmi in the background, BUT: they use different methods to track orphans = if you use both you should never use either's functionality to remove orphans, see Removing packages.

Mageia may Switch to DNF in future.

32 bit repos on 64 bit systems

Please note that on 64-bit systems, the 32-bit repositories are configured, but they are not enabled by default.

They are needed by some packages, such as Steam and Wine. If you want to install such packages that have dependencies on packages from 32-bit repositories, please make sure that you have "Core 32bit Release" and "Core 32bit Updates" enabled. Likewise for some cases the 32 bit Nonfree or Tainted (both in Release and Updates flavours) may be needed.

Important rules:

  • Don't enable a 32-bit repository without having the corresponding 64 bit repository enabled because 64-bits libs are preferred (generally) on 64-bit system.
  • If once a 32-bit repository is used, keep both its Release and Updates flavour enabled to not potentially hinder updates.

Warnings on non-Mageia packages

Warning!
Compatibility. When using external sources, please tell what external sources you have installed anything from whenever you report any problem on Mageia forum, mail list, bug report or other channels. Things can otherwise get confusing and unnecessary time consuming for all. Especially confusing it may be when the packages are named like Mageia packages, i.e containing ".mga7" as part of package name.

Also note that upgrading Mageia to next version may become problematic.

Also see Dependencies below.

Warning!
Security. Mageia naturally do not take any responsibility for any external package, be it RPM, AppImage, Flatpak, binary files... You are on your own to decide if you trust the software supplier regarding any security issue, malware etc. This may especially be an issue with closed source code applications. See mitigation tip in Security below.

External repos with Mageia packages

You may find a program you need packaged for Mageia, in a repository by the program creator or an enthusiast or organisation have packaged it and share.

Mageia enthusiasts

Other organisations

Examples:

Fedora COPR

Fedora COPR is a service provided by Fedora, used by many.

Examples:

Other repositories

Examples:

  • Opera web browser Mageia compatible RPM in repository at Fedora: Instructions using DNF package manager.

Universal package formats

There exist several ways to package software to make it easily installable on a lot of Linux distributions.

AppImage

AppImages are a kind of self-contained archives that can be downloaded and run directly without installation or the need for root rights; Just download one file, make it executable: chmod a+x FreeCAD*.AppImage, and run it: ./FreeCAD* . Given command examples are for when you open a console in the folder where you have downloaded the AppImage, i.e press F4 in Dolphin for the terminal.

More information at https://en.wikipedia.org/wiki/AppImage and https://appimage.org/ .

Programs can be found at the program authors sites, collected and structured at https://www.appimagehub.com/ , this list or a browsing/downloader/updater app AppImage Pool.

Examples: We have FreeCAD (a very capable mechanical CAD in heavy development) and Slic3r (3D printer CAM), but you may be interested in having the development versions to get extra features. You may still have the Mageia packaged version installed, or more than one version in AppImage format. https://forums.mageia.org/en/viewtopic.php?f=7&t=12200

AppImageUpdate can be run to update some AppImages to latest version. It is itself an AppImage, and can also update itself. As it uses delta updates, the downloads are very small and efficient. Note that you currently need to make a link to certificates. Unfortunately many AppImages are not prepared with required information for the updater to work. One good example though is FreeCAD, saving you a lot in download size. To check if an AppImage contain update information, issue ./thatprogram.AppImage --appimage-updateinformation; no output means no info.

Note:
If the AppImage application does not work because it is missing dependencies, that is a fault in the AppImage, as it is supposed to be self-contained. An incomplete AppImage may work on some distributions, and not on others. So if you see that problem, tell the application AppImage creator so they can fix the AppImage.

Flatpak

Flatpak is an utility for software deployment and package management for Linux.

With this you can install a vast range of applications more directly from developers, and independent from the rpm package system.

The Flatpak system maintains internal dependencies, installing what extra is needed automatically.

Programs are run sandboxed, except for rights asked at install time.

For further reading see our wiki page Flatpak.

Java jar files

Generally the most versatile also works on Microsoft and Apple systems. Some may need many dependencies, while some have everything included. Example: FriBok (Swedish invoice and accounting)

In general, just start a java program with java -jar thejarfile.jar

Nice to know: the .jar file is an archive that can be opened in i.e Ark, so you can i.e edit internal configuration files (i.e. I personalized my invoice formatting).

Using foreign rpm directly

With the normal caveat that it may not find its dependencies, there is also the (small) risk that the rpm may perform some pre/post-install scripts that do something you do not want.

Sometimes you just have to though. Here is an example installing a Canon printer driver using the vendor rpm but without using their install script.

Repackaging rpm

rpm packages from other Mageia release

In Mageia development release "Cauldron", there may exist a newer version you need of a program. You can then often download that rpm and rebuild it to suit the Mageia release you run, see How to do your own backports.

Foreign .rpm packages

An rpm from another distro can often be rebuilt for Mageia. Please refer to Packagers RPM tutorial. A good source for the best suitable package candidates is Fedora.

Also see our forum thread How to rebuild an src.rpm, using amoebax as example

.deb packages

Programs packaged for Debian/Ubuntu in .deb format can sometimes be converted using the program alien, which you can install from Mageia repo. - But Alien is broken mga#28607 and not maintained upstream. It seems that the package is not maintained for several years.

Alien was once intended as a program that could convert files from various formats to other formats, for example between the rpm format (Mageia, Redhat), dpkg (Debian), slp (Stampede), and tgz (Slackware). If you want to use a package from a Linux distribution other than the one you have installed on your PC, use Alien to convert such a package to your preferred package format. Then you install that converted package.


Old example: How to repackage and install Spotify

Binary files

Some have an installer script. It may be a good idea to look into the script to see what it does - you may want it in some other way, or not need to run it.

Some programs are just a binary file you set executable permission on, and run. Other may come as a .sh script with embedded/compressed binary at the end, that it unpacks when you run it. Other programs may come like a compressed folder tree you unpack where you want it, read any documents like readme and help files you find in it, and run the executable.

Like always it is good to start non-Mageia packaged programs the first time from the command line in a terminal so you see any messages, like missing dependencies.

In user home

Often programs are best installed in users /home/username/. Example: Eagle CAD (Proprietary printed circuit CAD)

For all users, i.e Acrobat Reader

These programs should end up in the /usr/local/ directory. This directory is intended for non-official packages.

Compiling the program yourself

The familiar trilogy:

./configure make make install

... Optionally making an rpm

Instead of that triology above, you can use checkinstall to generate an rpm:

./configure make checkinstall

You will then get an rpm that can be installed using urpmi, and can also be uninstalled when you want to. If the tarball already includes a good spec file, it is even easier:

rpmbuild -tb ballname.tar.gz

Qt programs

Mageia has the development suite so you may load the source in QtCreator and compile and launch it from there, also for debug, edit, development.

Or for just compiling it you can use qmake, see example for shematic program QElectroTech.

Running MSWindows programs

Wine

Wine can be used to translate system calls between MSWindows programs and the Linux system. It works for a lot of programs but not all. See: [1] and [2] .

For Wine integrated into Steam see Proton.

Sometimes Wine works, other times it doesn't work. There are several bug-reports still open, see there for workarounds.

mga#16273 : If launching a wine app gives warnings that suitable versions are missing, see this bug.

mga#28814 - Wine 32-bit install on 64-bit system doesn't pull mesa 32-bit drivers

mga#28840 - wine32 should require libjpeg.so.8

mga#31989 - WINE: Problematic WINEPREFIX; and dep version conflicts


Install from our repos:

  • on a 32 bit Mageia install wine. For support of 32 bit Microsoft Windows applications wine32 will be installed automatically.
  • on a 64 bit Mageia install wine64. If you need support for 32 bit Microsoft Windows applications you need to install wine32 additionally.

wine-mono and mingw64-wine-gecko / mingw32-wine-gecko get installed automatically as additional dependency.

For Wine32 and PlayOnLinux too, you may need to manually install libmesagl1 and libmesaglu1 mga#28814, and libjpeg8 mga#28840 as some programs need them.

Note:
In order to install wine32 on a 64-bit installation, the Core 32-bit Release and Core 32-bit Updates repositories must be enabled - Please read 32 bit repos on 64 bit systems.

Configure Wine by starting winecfg and launch programs directly by issuing wine PROGRAM [ARGUMENTS...].

For more thorough and more automated configuring including help to download libraries and programs: install from our repo and run q4wine. See home page. q4wine also includes the well known Winetricks application.

PlayOnLinux

PlayOnLinux installs games and programs developed for Microsoft Windows. Since not many games currently work directly under GNU/Linux, PlayOnLinux can be a solution to play Windows games within Linux.

Note:
PlayOnLinux will install Wine as dependency, and for wine32 on a 64 bit installation, the Core 32bit Release and Core 32bit Updates repositories must be enabled - Please read 32 bit repos on 64 bit systems.

Phoenicis PlayOnLinux

Phoenicis PlayOnLinux is the successor of PlayOnLinux. See Phoenicis on github. Possible to install via Flatpak.

Running DOS programs

In our repo you can find dosbox, and dosemu with the graphical extension xdosemu. There also is an image "dosemu-freedos" of FreeDOS, which is a free/libre alternative to MS DOS, for use with (x)dosemu. They use certain special features of the Linux kernel and the 80386+ processor. For more info read the package descriptions and search the net.

Emulators

Run "anything" for PC by using another OS

Emulate one or more other PC simultaneously and install the operating systems you need, and easily stop, start, clone, archive them.

Using virtualised PC hardware (see below), you can install almost any PC operating systems in one or more virtual PC - you can install DOS, Windows XP, 7, 10... or other Linux.

Emulate non-PC computers

Fancy old games? We have some emulators for DOS and various game consoles and old home computers, for which you can find games and other software on the internet or you maybe have them. Search for packages containing "emulator" in all packages summaries.

Game environments (and some apps too)

Also see Use Mageia to play Windows Games.

Steam

You can install Steam from our repo, and it provides an environment which can download and run games, and other software. A lot of software is available for more than one operating system. See here for Linux apps.

Note:
To install Steam you first need to enable 32 bit repositories - Please read 32 bit repos on 64 bit systems.

Some games may need you to select Nvidia or Intel icd.

Proton

Proton is a port by Valve of Wine. Proton is integrated into Steam as one of several compatibility layers Steam Play You can use Proton to play games made for MS Windows on Linux systems. How-to guide. Unofficial game compatibility database: ProtonDB

Lutris

We also have Lutris packaged, that installs and launches games from many platforms and eras. "Lutris is a video game preservation platform aiming to keep your video game collection up and running for the years to come." "We provide emulators, compatibility layers and game engine re-implementations".

Note that it depends on Wine to be installed, as it use its dependencies and drivers, although it use an own game optimised wine version to run the games.

If you have Hybrid Graphics (dual GPU), see paragraph Lutris configuration.

Flashpoint

Flashpoint (not packaged) supports games and animations created for a variety of web plugins and standards - not just Flash.

Heroic Game Launcher

To install Heroic Game Launcher, download the .rpm file directly from the official Heroic Games Launcher website [3] (select "Other" to download the .rpm)

Then use "Install software" (right-click on the downloaded .rpm) or install via terminal: 

rpm -i --nodeps heroic-2.9.2.x86_64.rpm


Each time there is a new Heroic version available you need to uninstall the old version and install the new one manually: 

urpme heroic-2.9.2.x86_64
rpm -i --nodeps heroic-2.10.0.x86_64.rpm

Deinstallation can also be done via MCC.

Common issues

Dependencies

Often foreign .rpm, converted .deb, binaries, .jar files, and some universal packages are dependant on one or more libraries. Usually, Mageia has them all, but under different names.

Try launching the program in a text terminal (i.e in konsole in Plasma), and it will often tell you what file it can not find. Then you can use urpmf or rpmdrake to search for it in a Mageia package and install that. If we have it in another place or slightly different version, you may be successful with symlinking or copying.

One common difference is that on Mageia the 64 bit libs are named lib64* but the rpm may need/look for the lib without the name "64".

Security

o Flatpak provides a kind of sandboxing in itself. For configuring, see Flatpak#Permissions.

o Firejail provides sandboxing for many programs, and is good for AppImage programs too. You need packages firejail and also firetools for configuring. Basic simple usage: prefix your program with "firejail". Or start firejail and from there your application. Using firetools: launch firetools and you see a pane with default quickstart links, and at top left two configuration links. For more information see links on the project page, man page, and the Arch Linux wiki page is good, as so often.

o Systems run under emulators like VirtualBox only share folders that you configure for sharing and can be read-only.

Containers

Containers offer an environment as close as possible as the one you'd get from a VM (Virtual Machine / vitualised hardware) but without the overhead that comes with running a separate kernel and simulating all the hardware. For more information see Wikipedia on OS-level virtualization. A good to the point introduction by RedHat is here.

In Mageia repos you find lxc, Docker (Wikipedia) and Podman. Some general Virtualisation Managers handle containers too.

Docker use a client-server architecture, while Podman use a daemonless architecture.

Virtualised hardware

For hardware virtualisation (Virtual Machine, VM - more or less emulate a computer and install OS on it) see our Virtualisation page. - VirtualBox, QEMU, KVM, Virt-Manager, Xen, are all packaged and VMware can be installed.

Cloud server

On Mageia you can install Nextcloud server which in turn can run a lot of plugin web applications like shared calendar, OnlyOffice, etc.

Nextcloud runs under the internet server Apache or Nginx. The server can run other things too, like Urpmi-proxy.

Even more ways...

Just short mentions, not to elaborate on here:

  • There exist great plugins/add-ons for web browsers (i.e Firefox) and other programs, macros for some programs, ...
  • You can execute command line scripts and the sort in various languages...
Retrieved from "https://wiki.mageia.org/mw-en/index.php?title=Ways_to_install_programs_pt-BR&oldid=63052"