EPKG Package Manager: Difference between revisions
EPKG instruction manual |
m corrected the compile-preserved in the right spot |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=== Epkg Package Manager === | === Epkg Package Manager === | ||
First of all, the holy '''epkg --help'''. | |||
== To install packages == | == To install packages == | ||
| Line 40: | Line 42: | ||
<code>epkg autoclean </code> | <code>epkg autoclean </code> | ||
== To upgrade also development & build packages == | |||
<code>epkg upgrade-full </code> | |||
No confirmation: | |||
<code>epkg autoupgrade-full </code> | |||
=== Package Administration === | |||
Argent comes with some Gentoo sets that you need to remove if you want KDE removed. | |||
Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''. | |||
But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing. | |||
So, basically you will have: | |||
<code>emerge --deselect plasma-workspace plasma-tools</code> | |||
Then, you can remove Plasma, and install something else. | |||
== If you are a developer, and want to start developing things with easy maintenance == | |||
You have to switch on development mode using <code>avasile --help</code> like this: | |||
<code>avasile --devmode </code> | |||
It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet. | |||
Normally a linux advanced user won't feel any difference between the normal user mode and devmode. | |||
But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''. | |||
In this mode you can start using epkg to compile things, like this: | |||
<code>epkg compile <package> </code> | |||
<code>epkg autocompile <package> </code> | |||
or | |||
<code>epkg recompile <package> </code> | |||
<code>epkg autorecompile <package> </code> | |||
Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile). | |||
== Compilation management == | |||
If you want to recompile every package that's based on a given package: | |||
<code>epkg recompile-depend <package> </code> | |||
No confirmation: | |||
<code>epkg autorecompile-depend <package> </code> | |||
Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages. | |||
=== Post kernel recompilation === | |||
If you are on development mode, after the reinstallation and upgrading of all kernels, you must use: | |||
<code>epkg module-rebuid</code> | |||
Or automated: | |||
<code>epkg automodule-rebuild</code> | |||
== If you get "preserved-rebuilds" warning == | |||
In order to compile the preserved-rebuild dependencies (that failed to compile for you): | |||
<code>epkg compile-preserved </code> | |||
No confirmation: | |||
<code>epkg autocompile-preserved </code> | |||
Latest revision as of 12:14, 18 June 2025
Epkg Package Manager
First of all, the holy epkg --help.
To install packages
epkg install <package>
No confirmation:
epkg autoinstall <package>
To remove packages
epkg remove <package>
No confirmation:
epkg autoremove <package>
To update
epkg update
No confirmation:
epkg autoupdate
To upgrade
epkg upgrade
No confirmation:
epkg autoupgrade
To clean after upgrade/install
epkg clean
No confirmation:
epkg autoclean
To upgrade also development & build packages
epkg upgrade-full
No confirmation:
epkg autoupgrade-full
Package Administration
Argent comes with some Gentoo sets that you need to remove if you want KDE removed.
Normally KDE Plasma can't be removed from Argent installation by a normal user - and this is the right way, it's like removing Windows 11 or MacOS UI.
But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.
So, basically you will have:
emerge --deselect plasma-workspace plasma-tools
Then, you can remove Plasma, and install something else.
If you are a developer, and want to start developing things with easy maintenance
You have to switch on development mode using avasile --help like this:
avasile --devmode
It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.
Normally a linux advanced user won't feel any difference between the normal user mode and devmode.
But essentially, the devmode will start installing build dependencies, and those dependencies are only used to compile or build programs.
In this mode you can start using epkg to compile things, like this:
epkg compile <package>
epkg autocompile <package>
or
epkg recompile <package>
epkg autorecompile <package>
Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).
Compilation management
If you want to recompile every package that's based on a given package:
epkg recompile-depend <package>
No confirmation:
epkg autorecompile-depend <package>
Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.
Post kernel recompilation
If you are on development mode, after the reinstallation and upgrading of all kernels, you must use:
epkg module-rebuid
Or automated:
epkg automodule-rebuild
If you get "preserved-rebuilds" warning
In order to compile the preserved-rebuild dependencies (that failed to compile for you):
epkg compile-preserved
No confirmation:
epkg autocompile-preserved
