2. Beyond Linux From Scratch 11.3
3. introduction_important_pkgmgt
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:>=translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Package Management	Package Management
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Package Management	Gestion de paquets
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Package Management	Gerenciamento de Pacote
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Package Management is an often requested addition to the LFS Book. A Package Manager allows tracking the installation of files making it easy to remove and upgrade packages. And before you begin to wonder, NO—this section does not talk about any particular package manager, nor does it recommend one. What it provides is a roundup of the more popular techniques and how they work. The perfect package manager for you may be among these techniques or may be a combination of two or more of these techniques. This section briefly mentions issues that may arise when upgrading packages.	Package Management is an often requested addition to the LFS Book. A Package Manager allows tracking the installation of files making it easy to remove and upgrade packages. And before you begin to wonder, NO—this section does not talk about any particular package manager, nor does it recommend one. What it provides is a roundup of the more popular techniques and how they work. The perfect package manager for you may be among these techniques or may be a combination of two or more of these techniques. This section briefly mentions issues that may arise when upgrading packages.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Package Management is an often requested addition to the LFS Book. A Package Manager allows tracking the installation of files making it easy to remove and upgrade packages. And before you begin to wonder, NO—this section does not talk about any particular package manager, nor does it recommend one. What it provides is a roundup of the more popular techniques and how they work. The perfect package manager for you may be among these techniques or may be a combination of two or more of these techniques. This section briefly mentions issues that may arise when upgrading packages.	La gestion de paquets est un ajout souvent demandé au livre LFS. Un gestionnaire de paquets permet de conserver une trace des fichiers installés, simplifiant ainsi la suppression ou la mise à jour des paquets. Avant toute chose, NON, cette section ne parle pas d'un gestionnaire de paquets particulier ni n'en recommande un. Elle fait une analyse des techniques les plus populaires et leur fonctionnement. Le gestionnaire de paquets parfait pourrait faire partie de ces techniques ou pourrait être une combinaison d'une ou plusieurs techniques. Cette section mentionne brièvement les problèmes pouvant survenir lors de la mise à jour des paquets.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Package Management is an often requested addition to the LFS Book. A Package Manager allows tracking the installation of files making it easy to remove and upgrade packages. And before you begin to wonder, NO—this section does not talk about any particular package manager, nor does it recommend one. What it provides is a roundup of the more popular techniques and how they work. The perfect package manager for you may be among these techniques or may be a combination of two or more of these techniques. This section briefly mentions issues that may arise when upgrading packages.	O Gerenciamento de Pacote é uma adição solicitada com frequência para o Livro LFS. Um Gerenciador de Pacote permite rastrear a instalação de arquivos, tornando fácil remover e atualizar pacotes. E, antes que você comece a questionar, NÃO—esta seção não fala acerca de qualquer gerenciador de pacote em particular; nem recomenda um. O que ela fornece é um resumo acerca das técnicas mais populares e como elas funcionam. O gerenciador de pacote perfeito para você possivelmente esteja entre essas técnicas ou possivelmente seja uma combinação de duas ou mais dessas técnicas. Esta seção menciona brevemente problemas que possivelmente surjam quando da atualização de pacotes.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Some reasons why no package manager is mentioned in LFS or BLFS:	Some reasons why no package manager is mentioned in LFS or BLFS:
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Some reasons why no package manager is mentioned in LFS or BLFS:	Quelques raisons de l'absence de mention d'un gestionnaire de paquets dans LFS ou BLFS :
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Some reasons why no package manager is mentioned in LFS or BLFS:	Algumas razões porque nenhum gerenciador de pacote é mencionado no LFS ou no BLFS:
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Dealing with package management takes the focus away from the goals of these books—teaching how a Linux system is built.	Dealing with package management takes the focus away from the goals of these books—teaching how a Linux system is built.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Dealing with package management takes the focus away from the goals of these books—teaching how a Linux system is built.	S'occuper de la gestion de paquets détourne l’attention des objectifs de ces livres qui est l’enseignement de la construction d’un système Linux.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Dealing with package management takes the focus away from the goals of these books—teaching how a Linux system is built.	Lidar com gerenciamento de pacote retira o foco das finalidades desses livros—ensinar como um sistema Linux é construído.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	There are multiple solutions for package management, each having its strengths and drawbacks. Including one that satisfies all audiences is difficult.	There are multiple solutions for package management, each having its strengths and drawbacks. Including one that satisfies all audiences is difficult.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	There are multiple solutions for package management, each having its strengths and drawbacks. Including one that satisfies all audiences is difficult.	Il existe de nombreuses solutions pour la gestion de paquets. Chacune ayant ses forces et ses faiblesses, en inclure une qui satisfera tout le monde est difficile.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	There are multiple solutions for package management, each having its strengths and drawbacks. Including one that satisfies all audiences is difficult.	Existem múltiplas soluções para gerenciamento de pacote, cada uma tendo seus pontos fortes e fracos. Incluir uma que satisfaça todas as audiências é difícil.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	There are some hints written on the topic of package management. Visit the <ulink url="&hints-root;">Hints subproject</ulink> and see if one of them fits your need.	There are some hints written on the topic of package management. Visit the <ulink url="&hints-root;">Hints subproject</ulink> and see if one of them fits your need.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	There are some hints written on the topic of package management. Visit the <ulink url="&hints-root;">Hints subproject</ulink> and see if one of them fits your need.	Des astuces ont été rédigées sur le thème de la gestion de paquets. Visitez le <ulink url="&hints-root;">sous-projet des astuces</ulink> et voyez celui qui satisfait vos besoins.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	There are some hints written on the topic of package management. Visit the <ulink url="&hints-root;">Hints subproject</ulink> and see if one of them fits your need.	Existem algumas dicas escritas no tópico acerca de gerenciamento de pacote. Visite o <ulink url="&hints-root;">sub projeto Dicas</ulink> e veja se uma delas se adéqua às suas necessidades.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Upgrade Issues	Upgrade Issues
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Upgrade Issues	Problèmes de mise à jour
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Upgrade Issues	Problemas de Atualização
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	A Package Manager makes it easy to upgrade to newer versions when they are released. Generally the instructions in the LFS and BLFS Book can be used to upgrade to the newer versions. Here are some points that you should be aware of when upgrading packages, especially on a running system.	A Package Manager makes it easy to upgrade to newer versions when they are released. Generally the instructions in the LFS and BLFS Book can be used to upgrade to the newer versions. Here are some points that you should be aware of when upgrading packages, especially on a running system.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	A Package Manager makes it easy to upgrade to newer versions when they are released. Generally the instructions in the LFS and BLFS Book can be used to upgrade to the newer versions. Here are some points that you should be aware of when upgrading packages, especially on a running system.	Un gestionnaire de paquets facilite les mises à jour vers les nouvelles versions au moment de leur sortie. Généralement, les instructions dans les livres LFS et BLFS peuvent être utilisées pour mettre à jour vers les nouvelles versions. Voici quelques points à connaître lors d’une mise à jour de paquets, spécialement sur un système en cours d’exécution.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	A Package Manager makes it easy to upgrade to newer versions when they are released. Generally the instructions in the LFS and BLFS Book can be used to upgrade to the newer versions. Here are some points that you should be aware of when upgrading packages, especially on a running system.	Um Gerenciador de Pacote torna fácil atualizar para versões mais novas quando elas são liberadas. Geralmente as instruções nos livros LFS e BLFS podem ser usadas para atualizar para versões mais novas. Aqui estão alguns pontos que você deveria estar ciente quando atualizar de pacotes, especialmente em um sistema em execução.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	If one of the toolchain packages (<application>Glibc</application>, <application>GCC</application> or <application>Binutils</application>) needs to be upgraded to a newer minor version, it is safer to rebuild LFS. Though you <emphasis>may</emphasis> be able to get by rebuilding all the packages in their dependency order, we do not recommend it. For example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer to rebuild. For micro version updates, a simple reinstallation usually works, but is not guaranteed. For example, upgrading from glibc-2.3.4 to glibc-2.3.5 will not usually cause any problems.	If one of the toolchain packages (<application>Glibc</application>, <application>GCC</application> or <application>Binutils</application>) needs to be upgraded to a newer minor version, it is safer to rebuild LFS. Though you <emphasis>may</emphasis> be able to get by rebuilding all the packages in their dependency order, we do not recommend it. For example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer to rebuild. For micro version updates, a simple reinstallation usually works, but is not guaranteed. For example, upgrading from glibc-2.3.4 to glibc-2.3.5 will not usually cause any problems.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	If one of the toolchain packages (<application>Glibc</application>, <application>GCC</application> or <application>Binutils</application>) needs to be upgraded to a newer minor version, it is safer to rebuild LFS. Though you <emphasis>may</emphasis> be able to get by rebuilding all the packages in their dependency order, we do not recommend it. For example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer to rebuild. For micro version updates, a simple reinstallation usually works, but is not guaranteed. For example, upgrading from glibc-2.3.4 to glibc-2.3.5 will not usually cause any problems.	Si un des paquets de l'ensemble d'outils (<application>Glibc</application>, <application>GCC</application> ou <application>Binutils</application>) doit être mis à jour avec une nouvelle version mineure, il est plus sûr de reconstruire LFS. Bien que vous <emphasis>pourriez</emphasis> être capable de reconstruire tous les paquets dans leur ordre de dépendances, nous ne le recommandons pas. Par exemple, si glibc-2.2.x a besoin d'être mis à jour vers glibc-2.3.x, il est préférable de reconstruire. Pour les mises à jour encore plus mineures, une simple réinstallation fonctionne généralement mais cela n'est pas garanti. Par exemple, mettre à jour de glibc-2.3.4 à glibc-2.3.5 ne causera en général aucun problème.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	If one of the toolchain packages (<application>Glibc</application>, <application>GCC</application> or <application>Binutils</application>) needs to be upgraded to a newer minor version, it is safer to rebuild LFS. Though you <emphasis>may</emphasis> be able to get by rebuilding all the packages in their dependency order, we do not recommend it. For example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer to rebuild. For micro version updates, a simple reinstallation usually works, but is not guaranteed. For example, upgrading from glibc-2.3.4 to glibc-2.3.5 will not usually cause any problems.	Se um dos pacotes do conjunto de ferramentas (<application>Glibc</application>; <application>GCC</application>; ou <application>Binutils</application>) precisar ser atualizado para uma versão mais recente menor, [então] é mais seguro reconstruir o LFS. Apesar de você <emphasis>possivelmente</emphasis> estar apto(a) a conseguir, via reconstrução de todos os pacotes na ordem de dependências deles, nós não recomendamos isso. Por exemplo, se o glibc-2.2.x precisar ser atualizado para o glibc-2.3.x, [então] é mais seguro reconstruir. Para micro atualizações de versão, uma reinstalação simples geralmente funciona, porém não é garantido. Por exemplo, atualizar do glibc-2.3.4 para o glibc-2.3.5 geralmente não causará quaisquer problemas.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	If a package containing a shared library is updated, and if the name of the library changes, then all the packages dynamically linked to the library need to be recompiled to link against the newer library. (Note that there is no correlation between the package version and the name of the library.) For example, consider a package foo-1.2.3 that installs a shared library with name <filename class='libraryfile'>libfoo.so.1</filename>. Say you upgrade the package to a newer version foo-1.2.4 that installs a shared library with name <filename class='libraryfile'>libfoo.so.2</filename>. In this case, all packages that are dynamically linked to <filename class='libraryfile'>libfoo.so.1</filename> need to be recompiled to link against <filename class='libraryfile'>libfoo.so.2</filename>. Note that you should not remove the previous libraries until the dependent packages are recompiled.	If a package containing a shared library is updated, and if the name of the library changes, then all the packages dynamically linked to the library need to be recompiled to link against the newer library. (Note that there is no correlation between the package version and the name of the library.) For example, consider a package foo-1.2.3 that installs a shared library with name <filename class='libraryfile'>libfoo.so.1</filename>. Say you upgrade the package to a newer version foo-1.2.4 that installs a shared library with name <filename class='libraryfile'>libfoo.so.2</filename>. In this case, all packages that are dynamically linked to <filename class='libraryfile'>libfoo.so.1</filename> need to be recompiled to link against <filename class='libraryfile'>libfoo.so.2</filename>. Note that you should not remove the previous libraries until the dependent packages are recompiled.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	If a package containing a shared library is updated, and if the name of the library changes, then all the packages dynamically linked to the library need to be recompiled to link against the newer library. (Note that there is no correlation between the package version and the name of the library.) For example, consider a package foo-1.2.3 that installs a shared library with name <filename class='libraryfile'>libfoo.so.1</filename>. Say you upgrade the package to a newer version foo-1.2.4 that installs a shared library with name <filename class='libraryfile'>libfoo.so.2</filename>. In this case, all packages that are dynamically linked to <filename class='libraryfile'>libfoo.so.1</filename> need to be recompiled to link against <filename class='libraryfile'>libfoo.so.2</filename>. Note that you should not remove the previous libraries until the dependent packages are recompiled.	Si un paquet contenant une bibliothèque partagée est mis à jour et si le nom de cette dernière est modifié, alors tous les paquets liés dynamiquement à la bibliothèque devront être recompilés pour être liés à la nouvelle bibliothèque. (Remarquez qu'il n'y a aucune corrélation entre la version du paquet et le nom de la bibliothèque.) Par exemple, imaginez un paquet foo-1.2.3 qui installe une bibliothèque partagée de nom <filename class='libraryfile'>libtoto.so.1</filename>. Disons que vous mettez à jour le paquet avec une nouvelle version foo-1.2.4 qui installe une bibliothèque partagée de nom <filename class='libraryfile'>libtoto.so.2</filename>. Dans ce cas, tous les paquets liés dynamiquement à <filename class='libraryfile'>libtoto.so.1</filename> doivent être recompilés pour être liés à <filename class='libraryfile'>libtoto.so.2</filename>. Remarquez que vous ne devriez pas supprimer les anciennes bibliothèques jusqu'à ce que les paquets dépendants soient recompilés.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	If a package containing a shared library is updated, and if the name of the library changes, then all the packages dynamically linked to the library need to be recompiled to link against the newer library. (Note that there is no correlation between the package version and the name of the library.) For example, consider a package foo-1.2.3 that installs a shared library with name <filename class='libraryfile'>libfoo.so.1</filename>. Say you upgrade the package to a newer version foo-1.2.4 that installs a shared library with name <filename class='libraryfile'>libfoo.so.2</filename>. In this case, all packages that are dynamically linked to <filename class='libraryfile'>libfoo.so.1</filename> need to be recompiled to link against <filename class='libraryfile'>libfoo.so.2</filename>. Note that you should not remove the previous libraries until the dependent packages are recompiled.	Se um pacote contendo uma biblioteca compartilhada for atualizado e se o nome da biblioteca mudar, então todos os pacotes vinculados dinamicamente à biblioteca precisam ser recompilados para vincular contra a biblioteca mais recente. (Observe que não existe correlação entre a versão do pacote e o nome da biblioteca). Por exemplo, considere um pacote foo-1.2.3 que instala uma biblioteca compartilhada com nome <filename class='libraryfile'>libfoo.so.1</filename>. Digamos que você atualize o pacote para uma versão mais recente foo-1.2.4 que instala uma biblioteca compartilhada com nome <filename class='libraryfile'>libfoo.so.2</filename>. Nesse caso, todos os pacotes que estiverem vinculados dinamicamente a <filename class='libraryfile'>libfoo.so.1</filename> precisam ser recompilados para vincular contra <filename class='libraryfile'>libfoo.so.2</filename>. Observe que você não deveria remover as bibliotecas anteriores até que os pacotes dependentes sejam recompilados.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	If you are upgrading a running system, be on the lookout for packages that use <command>cp</command> instead of <command>install</command> to install files. The latter command is usually safer if the executable or library is already loaded in memory.	If you are upgrading a running system, be on the lookout for packages that use <command>cp</command> instead of <command>install</command> to install files. The latter command is usually safer if the executable or library is already loaded in memory.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	If you are upgrading a running system, be on the lookout for packages that use <command>cp</command> instead of <command>install</command> to install files. The latter command is usually safer if the executable or library is already loaded in memory.	Si vous mettez à jour un système en cours d’exécution, cherchez des paquets qui utilisent <command>cp</command> à la place de <command>install</command> pour installer des fichiers. La dernière commande est en général plus sûre si l'exécutable ou la bibliothèque est déjà chargé en mémoire.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	If you are upgrading a running system, be on the lookout for packages that use <command>cp</command> instead of <command>install</command> to install files. The latter command is usually safer if the executable or library is already loaded in memory.	Se você estiver atualizando um sistema em execução, [então] esteja atento(a) a pacotes que usam o <command>cp</command> em vez do <command>install</command> para instalar arquivos. O último comando geralmente é mais seguro se o executável ou biblioteca já estiver carregado(a) na memória.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Package Management Techniques	Package Management Techniques
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Package Management Techniques	Techniques de gestion de paquets
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Package Management Techniques	Técnicas de Gerenciamento de Pacote
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	The following are some common package management techniques. Before making a decision on a package manager, do some research on the various techniques, particularly the drawbacks of the particular scheme.	The following are some common package management techniques. Before making a decision on a package manager, do some research on the various techniques, particularly the drawbacks of the particular scheme.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	The following are some common package management techniques. Before making a decision on a package manager, do some research on the various techniques, particularly the drawbacks of the particular scheme.	Voici une liste de techniques habituelles de gestion de paquets. Avant de vous décider sur un gestionnaire de paquets, faites une recherche sur les différentes techniques et notamment leurs faiblesses.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	The following are some common package management techniques. Before making a decision on a package manager, do some research on the various techniques, particularly the drawbacks of the particular scheme.	As seguintes são algumas técnicas comuns de gerenciamento de pacote. Antes de se decidir acerca de um gerenciador de pacote, pesquise sobre as várias técnicas, particularmente os pontos fracos do esquema em particular.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	It is All in My Head!	It is All in My Head!
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	It is All in My Head!	Tout est dans ma tête&nbsp;!
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	It is All in My Head!	Está Tudo na Minha Cabeça!
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Yes, this is a package management technique. Some folks do not find the need for a package manager because they know the packages intimately and know what files are installed by each package. Some users also do not need any package management because they plan on rebuilding the entire system when a package is changed.	Yes, this is a package management technique. Some folks do not find the need for a package manager because they know the packages intimately and know what files are installed by each package. Some users also do not need any package management because they plan on rebuilding the entire system when a package is changed.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Yes, this is a package management technique. Some folks do not find the need for a package manager because they know the packages intimately and know what files are installed by each package. Some users also do not need any package management because they plan on rebuilding the entire system when a package is changed.	Oui, c'est une technique de gestion de paquets. Certains n'éprouvent pas le besoin d'utiliser un gestionnaire de paquets parce qu'ils connaissent très bien les paquets et connaissent les fichiers installés par chaque paquet. Certains utilisateurs n'en ont pas besoin parce qu'ils prévoient de reconstruire entièrement LFS lorsqu'un paquet est modifié.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Yes, this is a package management technique. Some folks do not find the need for a package manager because they know the packages intimately and know what files are installed by each package. Some users also do not need any package management because they plan on rebuilding the entire system when a package is changed.	Sim, essa é uma técnica de gerenciamento de pacote. Algumas pessoas não encontram a necessidade para um gerenciador de pacote, pois elas conhecem os pacotes intimamente e sabem quais arquivos são instalados por cada pacote. Alguns(as) usuários(as) também não precisam de qualquer gerenciamento de pacote, pois eles(as) planejam reconstruir o sistema inteiro quando um pacote for mudado.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Install in Separate Directories	Install in Separate Directories
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Install in Separate Directories	Installer dans des répertoires séparés
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Install in Separate Directories	Instalação em Diretórios Separados
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	This is a simplistic package management that does not need any extra package to manage the installations. Each package is installed in a separate directory. For example, package foo-1.1 is installed in <filename class='directory'>/usr/pkg/foo-1.1</filename> and a symlink is made from <filename>/usr/pkg/foo</filename> to <filename class='directory'>/usr/pkg/foo-1.1</filename>. When installing a new version foo-1.2, it is installed in <filename class='directory'>/usr/pkg/foo-1.2</filename> and the previous symlink is replaced by a symlink to the new version.	This is a simplistic package management that does not need any extra package to manage the installations. Each package is installed in a separate directory. For example, package foo-1.1 is installed in <filename class='directory'>/usr/pkg/foo-1.1</filename> and a symlink is made from <filename>/usr/pkg/foo</filename> to <filename class='directory'>/usr/pkg/foo-1.1</filename>. When installing a new version foo-1.2, it is installed in <filename class='directory'>/usr/pkg/foo-1.2</filename> and the previous symlink is replaced by a symlink to the new version.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	This is a simplistic package management that does not need any extra package to manage the installations. Each package is installed in a separate directory. For example, package foo-1.1 is installed in <filename class='directory'>/usr/pkg/foo-1.1</filename> and a symlink is made from <filename>/usr/pkg/foo</filename> to <filename class='directory'>/usr/pkg/foo-1.1</filename>. When installing a new version foo-1.2, it is installed in <filename class='directory'>/usr/pkg/foo-1.2</filename> and the previous symlink is replaced by a symlink to the new version.	C'est une gestion des paquets simple qui ne nécessite aucun paquet supplémentaire pour gérer les installations. Chaque paquet est installé dans un répertoire séparé. Par exemple, le paquet foo-1.1 est installé dans <filename class='directory'>/usr/pkg/foo-1.1</filename> et un lien symbolique est créé de <filename>/usr/pkg/foo</filename> vers <filename class='directory'>/usr/pkg/foo-1.1</filename>. Lors de l'installation de la nouvelle version foo-1.2, elle est installée dans <filename class='directory'>/usr/pkg/foo-1.2</filename> et l'ancien lien symbolique est remplacé par un lien symbolique vers la nouvelle version.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	This is a simplistic package management that does not need any extra package to manage the installations. Each package is installed in a separate directory. For example, package foo-1.1 is installed in <filename class='directory'>/usr/pkg/foo-1.1</filename> and a symlink is made from <filename>/usr/pkg/foo</filename> to <filename class='directory'>/usr/pkg/foo-1.1</filename>. When installing a new version foo-1.2, it is installed in <filename class='directory'>/usr/pkg/foo-1.2</filename> and the previous symlink is replaced by a symlink to the new version.	Esse é um gerenciamento de pacote simplista que não necessita de qualquer pacote extra para gerenciar as instalações. Cada pacote é instalado em um diretório separado. Por exemplo, o pacote foo-1.1 é instalado em <filename class='directory'>/usr/pkg/foo-1.1</filename> e um link simbólico é feito de <filename>/usr/pkg/foo</filename> para <filename class='directory'>/usr/pkg/foo-1.1</filename>. Quando se instalar uma nova versão foo-1.2, ela é instalada em <filename class='directory'>/usr/pkg/foo-1.2</filename> e o link simbólico anterior é substituído por um link simbólico para a nova versão.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	The environment variables such as those mentioned in <quote><xref linkend="beyond"/></quote> need to be expanded to include <filename>/usr/pkg/foo</filename>. For more than a few packages, this scheme becomes unmanageable.	The environment variables such as those mentioned in <quote><xref linkend="beyond"/></quote> need to be expanded to include <filename>/usr/pkg/foo</filename>. For more than a few packages, this scheme becomes unmanageable.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	The environment variables such as those mentioned in <quote><xref linkend="beyond"/></quote> need to be expanded to include <filename>/usr/pkg/foo</filename>. For more than a few packages, this scheme becomes unmanageable.	Les variables d'environnement telles que celles indiquées dans <quote><xref linkend="beyond"/></quote> ont besoin d'être étendues pour inclure <filename>/usr/pkg/foo</filename>. Ce schéma devient ingérable dans le cas d’un trop gros nombre de paquets.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	The environment variables such as those mentioned in <quote><xref linkend="beyond"/></quote> need to be expanded to include <filename>/usr/pkg/foo</filename>. For more than a few packages, this scheme becomes unmanageable.	As Variáveis de ambiente, tais como aquelas mencionadas em <quote><xref linkend="beyond"/></quote>, precisam ser expandidas para incluir <filename>/usr/pkg/foo</filename>. Para mais que uns poucos pacotes, esse esquema se torna ingerenciável.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Symlink Style Package Management	Symlink Style Package Management
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Symlink Style Package Management	Gestion de paquet par lien symbolique
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Symlink Style Package Management	Gerenciamento de Pacote Estilo Link Simbólico
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	This is a variation of the previous package management technique. Each package is installed similar to the previous scheme. But instead of making the symlink, each file is symlinked into the <filename class='directory'>/usr</filename> hierarchy. This removes the need to expand the environment variables. Though the symlinks can be created by the user to automate the creation, many package managers have been written using this approach. A few of the popular ones are Stow, Epkg, Graft, and Depot.	This is a variation of the previous package management technique. Each package is installed similar to the previous scheme. But instead of making the symlink, each file is symlinked into the <filename class='directory'>/usr</filename> hierarchy. This removes the need to expand the environment variables. Though the symlinks can be created by the user to automate the creation, many package managers have been written using this approach. A few of the popular ones are Stow, Epkg, Graft, and Depot.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	This is a variation of the previous package management technique. Each package is installed similar to the previous scheme. But instead of making the symlink, each file is symlinked into the <filename class='directory'>/usr</filename> hierarchy. This removes the need to expand the environment variables. Though the symlinks can be created by the user to automate the creation, many package managers have been written using this approach. A few of the popular ones are Stow, Epkg, Graft, and Depot.	C'est une variante de la technique précédente. Chaque paquet est installé de façon similaire au schéma précédent. Mais au lieu de réaliser le lien symbolique, chaque fichier dispose d'un lien symbolique vers son équivalent dans la hiérarchie <filename class='directory'>/usr</filename>. Ceci supprime le besoin d'étendre les variables d'environnement. Bien que les liens symboliques puissent être créés par l'utilisateur, pour en automatiser la création, certains gestionnaires de paquets ont été écrits avec cette approche. Parmi les plus populaires se trouvent Stow, Epkg, Graft et Depot.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	This is a variation of the previous package management technique. Each package is installed similar to the previous scheme. But instead of making the symlink, each file is symlinked into the <filename class='directory'>/usr</filename> hierarchy. This removes the need to expand the environment variables. Though the symlinks can be created by the user to automate the creation, many package managers have been written using this approach. A few of the popular ones are Stow, Epkg, Graft, and Depot.	Essa é uma variação da técnica de gerenciamento de pacote anterior. Cada pacote é instalado similar ao esquema anterior. Mas, em vez de fazer o link simbólico, cada arquivo é simbolicamente vinculado à hierarquia <filename class='directory'>/usr</filename>. Isso remove a necessidade de expandir as variáveis de ambiente. Ainda que os links simbólicos possam ser criados pelo(a) usuário(a) para automatizar a criação, muitos gerenciadores de pacote tem sido escritos usando essa abordagem. Alguns dos populares são Stow, Epkg, Graft e Depot.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	The installation needs to be faked, so that the package thinks that it is installed in <filename class="directory">/usr</filename> though in reality it is installed in the <filename class="directory">/usr/pkg</filename> hierarchy. Installing in this manner is not usually a trivial task. For example, consider that you are installing a package libfoo-1.1. The following instructions may not install the package properly:	The installation needs to be faked, so that the package thinks that it is installed in <filename class="directory">/usr</filename> though in reality it is installed in the <filename class="directory">/usr/pkg</filename> hierarchy. Installing in this manner is not usually a trivial task. For example, consider that you are installing a package libfoo-1.1. The following instructions may not install the package properly:
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	The installation needs to be faked, so that the package thinks that it is installed in <filename class="directory">/usr</filename> though in reality it is installed in the <filename class="directory">/usr/pkg</filename> hierarchy. Installing in this manner is not usually a trivial task. For example, consider that you are installing a package libfoo-1.1. The following instructions may not install the package properly:	L'installation doit être faussée, de façon à ce que chaque paquet pense qu'il est installé dans <filename class="directory">/usr</filename> alors qu'en réalité il est installé dans la hiérarchie <filename class="directory">/usr/pkg</filename>. Installer de cette manière n'est généralement pas une tâche aisée. Par exemple, imaginez que vous installez un paquet libtoto-1.1. Les instructions suivantes pourraient ne pas installer correctement le paquet&nbsp;:
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	The installation needs to be faked, so that the package thinks that it is installed in <filename class="directory">/usr</filename> though in reality it is installed in the <filename class="directory">/usr/pkg</filename> hierarchy. Installing in this manner is not usually a trivial task. For example, consider that you are installing a package libfoo-1.1. The following instructions may not install the package properly:	A instalação precisa ser falseada, de modo que o pacote pense que está instalado em <filename class="directory">/usr</filename>, ainda que, na realidade, ele esteja instalado na hierarquia <filename class="directory">/usr/pkg</filename>. Instalar dessa maneira geralmente não é uma tarefa trivial. Por exemplo, considere que você está instalando um pacote libfoo-1.1. As seguintes instruções possivelmente não instalem adequadamente o pacote:
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	<userinput>./configure --prefix=/usr/pkg/libfoo/1.1 make make install</userinput>	<userinput>./configure --prefix=/usr/pkg/libfoo/1.1 make make install</userinput>
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	<userinput>./configure --prefix=/usr/pkg/libfoo/1.1 make make install</userinput>	<userinput>./configure --prefix=/usr/pkg/libtoto/1.1 make make install</userinput>
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	<userinput>./configure --prefix=/usr/pkg/libfoo/1.1 make make install</userinput>	<userinput>./configure --prefix=/usr/pkg/libfoo/1.1 make make install</userinput>
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	The installation will work, but the dependent packages may not link to libfoo as you would expect. If you compile a package that links against libfoo, you may notice that it is linked to <filename class='libraryfile'>/usr/pkg/libfoo/1.1/lib/libfoo.so.1</filename> instead of <filename class='libraryfile'>/usr/lib/libfoo.so.1</filename> as you would expect. The correct approach is to use <envar>DESTDIR</envar> strategy to fake installation of the package. This approach works as follows:	The installation will work, but the dependent packages may not link to libfoo as you would expect. If you compile a package that links against libfoo, you may notice that it is linked to <filename class='libraryfile'>/usr/pkg/libfoo/1.1/lib/libfoo.so.1</filename> instead of <filename class='libraryfile'>/usr/lib/libfoo.so.1</filename> as you would expect. The correct approach is to use <envar>DESTDIR</envar> strategy to fake installation of the package. This approach works as follows:
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	The installation will work, but the dependent packages may not link to libfoo as you would expect. If you compile a package that links against libfoo, you may notice that it is linked to <filename class='libraryfile'>/usr/pkg/libfoo/1.1/lib/libfoo.so.1</filename> instead of <filename class='libraryfile'>/usr/lib/libfoo.so.1</filename> as you would expect. The correct approach is to use <envar>DESTDIR</envar> strategy to fake installation of the package. This approach works as follows:	L'installation fonctionnera mais les paquets dépendants pourraient ne pas lier libtoto comme vous vous y attendriez. Si vous compilez un paquet qui se lie à libtoto, vous pourrez remarquer qu'il se lie à <filename class='libraryfile'>/usr/pkg/libtoto/1.1/lib/libtoto.so.1</filename> au lieu de <filename class='libraryfile'>/usr/lib/libtoto.so.1</filename> comme vous le prévoyiez. La bonne approche est d'utiliser la stratégie <envar>DESTDIR</envar> pour fausser l'installation du paquet. Cette approche fonctionne ainsi&nbsp;:
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	The installation will work, but the dependent packages may not link to libfoo as you would expect. If you compile a package that links against libfoo, you may notice that it is linked to <filename class='libraryfile'>/usr/pkg/libfoo/1.1/lib/libfoo.so.1</filename> instead of <filename class='libraryfile'>/usr/lib/libfoo.so.1</filename> as you would expect. The correct approach is to use <envar>DESTDIR</envar> strategy to fake installation of the package. This approach works as follows:	A instalação funcionará, mas os pacotes dependentes possivelmente não se vinculem à libfoo conforme você esperaria. Se você compilar um pacote que vincula à libfoo, [então] você possivelmente note que ele está vinculado a <filename class='libraryfile'>/usr/pkg/libfoo/1.1/lib/libfoo.so.1</filename> em vez de <filename class='libraryfile'>/usr/lib/libfoo.so.1</filename> como você esperaria. A abordagem correta é a de usar a estratégia <envar>DESTDIR</envar> para falsear a instalação do pacote. Essa abordagem funciona como se segue:
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	<userinput>./configure --prefix=/usr make make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput>	<userinput>./configure --prefix=/usr make make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput>
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	<userinput>./configure --prefix=/usr make make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput>	<userinput>./configure --prefix=/usr make make DESTDIR=/usr/pkg/libtoto/1.1 install</userinput>
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	<userinput>./configure --prefix=/usr make make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput>	<userinput>./configure --prefix=/usr make make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput>
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Most of the packages do support this approach, but there are some which do not. For the non-compliant packages, you may either need to manually install the package, or you may find that it is easier to install some problematic packages into <filename class='directory'>/opt</filename>.	Most of the packages do support this approach, but there are some which do not. For the non-compliant packages, you may either need to manually install the package, or you may find that it is easier to install some problematic packages into <filename class='directory'>/opt</filename>.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Most of the packages do support this approach, but there are some which do not. For the non-compliant packages, you may either need to manually install the package, or you may find that it is easier to install some problematic packages into <filename class='directory'>/opt</filename>.	La plupart des paquets prennent en charge cette approche mais elle pose problème à certains. Pour les paquets non compatibles, vous devrez les installer manuellement, ou alors vous pouvez trouver plus simple d'installer les paquets problématiques dans <filename class='directory'>/opt</filename>.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Most of the packages do support this approach, but there are some which do not. For the non-compliant packages, you may either need to manually install the package, or you may find that it is easier to install some problematic packages into <filename class='directory'>/opt</filename>.	A maioria dos pacotes suporta essa abordagem, mas existem alguns que não. Para os pacotes não conformes, você possivelmente ou precise instalar manualmente o pacote, ou você possivelmente ache que é mais fácil instalar alguns pacotes problemáticos em <filename class='directory'>/opt</filename>.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Timestamp Based	Timestamp Based
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Timestamp Based	Basé sur l'horodatage
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Timestamp Based	Baseado em Carimbo de Tempo
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	In this technique, a file is timestamped before the installation of the package. After the installation, a simple use of the <command>find</command> command with the appropriate options can generate a log of all the files installed after the timestamp file was created. A package manager written with this approach is install-log.	In this technique, a file is timestamped before the installation of the package. After the installation, a simple use of the <command>find</command> command with the appropriate options can generate a log of all the files installed after the timestamp file was created. A package manager written with this approach is install-log.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	In this technique, a file is timestamped before the installation of the package. After the installation, a simple use of the <command>find</command> command with the appropriate options can generate a log of all the files installed after the timestamp file was created. A package manager written with this approach is install-log.	Avec cette technique, un fichier est horodaté avant l'installation du paquet. Après l'installation, une simple utilisation de la commande <command>find</command> avec les options appropriées peut générer un journal de tous les fichiers installés après la création du fichier horodaté. install-log est un gestionnaire de paquets écrit avec cette approche.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	In this technique, a file is timestamped before the installation of the package. After the installation, a simple use of the <command>find</command> command with the appropriate options can generate a log of all the files installed after the timestamp file was created. A package manager written with this approach is install-log.	Nessa técnica, um arquivo é carimbado temporalmente antes da instalação do pacote. Após a instalação, um simples uso do comando <command>find</command> com as opções apropriadas pode gerar um registro de todos os arquivos instalados após o arquivo de carimbo de tempo ser criado. Um gerenciador de pacote escrito com essa abordagem é instalação-registro.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Though this scheme has the advantage of being simple, it has two drawbacks. If during installation, the files are installed with any timestamp other than the current time, those files will not be tracked by the package manager. Also, this scheme can only be used when one package is installed at a time. The logs are not reliable if two packages are being installed on two different consoles.	Though this scheme has the advantage of being simple, it has two drawbacks. If during installation, the files are installed with any timestamp other than the current time, those files will not be tracked by the package manager. Also, this scheme can only be used when one package is installed at a time. The logs are not reliable if two packages are being installed on two different consoles.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Though this scheme has the advantage of being simple, it has two drawbacks. If during installation, the files are installed with any timestamp other than the current time, those files will not be tracked by the package manager. Also, this scheme can only be used when one package is installed at a time. The logs are not reliable if two packages are being installed on two different consoles.	Bien que ce schéma a l'avantage d'être simple, il a deux inconvénients. Si à l'installation, les fichiers sont installés avec un horodatage autre que celui de l'heure actuelle, ces fichiers ne seront pas suivis par le gestionnaire de paquets. De plus, ce schéma peut seulement être utilisé lorsqu'un seul paquet est installé à la fois. Les registres ne sont pas fiables si deux paquets sont installés dans deux consoles différentes.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Though this scheme has the advantage of being simple, it has two drawbacks. If during installation, the files are installed with any timestamp other than the current time, those files will not be tracked by the package manager. Also, this scheme can only be used when one package is installed at a time. The logs are not reliable if two packages are being installed on two different consoles.	Ainda que esse esquema tenha a vantagem de ser simples, ele tem duas desvantagens. Se, durante a instalação, os arquivos forem instalados com qualquer carimbo de tempo outro que a hora atual, [então] aqueles arquivos não serão rastreados pelo gerenciador de pacote. Além disso, esse esquema pode ser usado somente quando um pacote for instalado de cada vez. Os registros não são confiáveis se dois pacotes estiverem sendo instalados em dois consoles.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	LD_PRELOAD Based	LD_PRELOAD Based
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	LD_PRELOAD Based	Basé sur LD_PRELOAD
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	LD_PRELOAD Based	Baseado em LD_PRELOAD
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	In this approach, a library is preloaded before installation. During installation, this library tracks the packages that are being installed by attaching itself to various executables such as <command>cp</command>, <command>install</command>, <command>mv</command> and tracking the system calls that modify the filesystem. For this approach to work, all the executables need to be dynamically linked without the suid or sgid bit. Preloading the library may cause some unwanted side-effects during installation. Therefore, do perform some tests to ensure that the package manager does not break anything and logs all the appropriate files.	In this approach, a library is preloaded before installation. During installation, this library tracks the packages that are being installed by attaching itself to various executables such as <command>cp</command>, <command>install</command>, <command>mv</command> and tracking the system calls that modify the filesystem. For this approach to work, all the executables need to be dynamically linked without the suid or sgid bit. Preloading the library may cause some unwanted side-effects during installation. Therefore, do perform some tests to ensure that the package manager does not break anything and logs all the appropriate files.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	In this approach, a library is preloaded before installation. During installation, this library tracks the packages that are being installed by attaching itself to various executables such as <command>cp</command>, <command>install</command>, <command>mv</command> and tracking the system calls that modify the filesystem. For this approach to work, all the executables need to be dynamically linked without the suid or sgid bit. Preloading the library may cause some unwanted side-effects during installation. Therefore, do perform some tests to ensure that the package manager does not break anything and logs all the appropriate files.	Avec cette approche, une bibliothèque est préchargée avant l'installation. Pendant l'installation, cette bibliothèque suit les paquets qui sont installés en s'attachant à divers exécutables tels que <command>cp</command>, <command>install</command>, <command>mv</command> et en suivant les appels système qui modifient le système de fichiers. Pour que cette approche fonctionne, tous les exécutables doivent être liés de façon dynamique sans le bit suid ou sgid (id super utilisateur ou super groupe). Le préchargement de la bibliothèque peut provoquer des effets indésirables pendant l'installation. Effectuez donc des tests pour vous assurer que le gestionnaire de paquets ne casse rien et journalise tous les fichiers adéquats.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	In this approach, a library is preloaded before installation. During installation, this library tracks the packages that are being installed by attaching itself to various executables such as <command>cp</command>, <command>install</command>, <command>mv</command> and tracking the system calls that modify the filesystem. For this approach to work, all the executables need to be dynamically linked without the suid or sgid bit. Preloading the library may cause some unwanted side-effects during installation. Therefore, do perform some tests to ensure that the package manager does not break anything and logs all the appropriate files.	Nessa abordagem, uma biblioteca é pré carregada antes da instalação. Durante a instalação, essa biblioteca rastreia os pacotes que estão sendo instalados anexando-se a vários executáveis, tais como <command>cp</command>; <command>install</command>; <command>mv</command>, e rastreando as chamadas de sistema que modificam o sistema de arquivos. Para que essa abordagem funcione, todos os executáveis precisam ser dinamicamente vinculados sem o bit suid ou sgid. Pré-carregar a biblioteca possivelmente cause alguns efeitos colaterais indesejados durante a instalação. Portanto, aconselha-se que se realize alguns testes para garantir que o gerenciador de pacote não quebre nada e registre todos os arquivos adequados.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	Creating Package Archives	Creating Package Archives
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	Creating Package Archives	Créer des archives de paquets
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	Creating Package Archives	Criando Arquivamentos de Pacote
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	In this scheme, the package installation is faked into a separate tree as described in the Symlink style package management. After the installation, a package archive is created using the installed files. This archive is then used to install the package either on the local machine or can even be used to install the package on other machines.	In this scheme, the package installation is faked into a separate tree as described in the Symlink style package management. After the installation, a package archive is created using the installed files. This archive is then used to install the package either on the local machine or can even be used to install the package on other machines.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	In this scheme, the package installation is faked into a separate tree as described in the Symlink style package management. After the installation, a package archive is created using the installed files. This archive is then used to install the package either on the local machine or can even be used to install the package on other machines.	Dans ce schéma, l'installation d'un paquet est faussée dans un répertoire séparé comme précédemment décrit dans la gestion de paquet par lien symbolique. Après l'installation, une archive du paquet est créée en utilisant les fichiers installés. L'archive est ensuite utilisée pour installer le paquet sur la machine locale voire même sur d'autres machines.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	In this scheme, the package installation is faked into a separate tree as described in the Symlink style package management. After the installation, a package archive is created using the installed files. This archive is then used to install the package either on the local machine or can even be used to install the package on other machines.	Nesse esquema, a instalação do pacote é falseada em uma árvore separada como descrito no gerenciamento de pacote estilo Link Simbólico. Após a instalação, um arquivamento de pacote é criado usando os arquivos instalados. Esse arquivamento é então usado para instalar o pacote tanto na máquina local quanto pode até ser usado para instalar o pacote em outras máquinas.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	This approach is used by most of the package managers found in the commercial distributions. Examples of package managers that follow this approach are RPM, pkg-utils, Debian's apt, and Gentoo's Portage system.	This approach is used by most of the package managers found in the commercial distributions. Examples of package managers that follow this approach are RPM, pkg-utils, Debian's apt, and Gentoo's Portage system.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — French	This approach is used by most of the package managers found in the commercial distributions. Examples of package managers that follow this approach are RPM, pkg-utils, Debian's apt, and Gentoo's Portage system.	Cette approche est utilisée par la plupart des gestionnaires de paquets trouvés dans les distributions commerciales. Les exemples de gestionnaires qui suivent cette approche sont RPM, pkg-utils, apt de Debian et le système Portage de Gentoo.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — Portuguese (Brazil)	This approach is used by most of the package managers found in the commercial distributions. Examples of package managers that follow this approach are RPM, pkg-utils, Debian's apt, and Gentoo's Portage system.	Essa abordagem é usada pela maioria dos gerenciadores de pacote encontrados nas distribuições comerciais. Exemplos de gerenciadores de pacote que seguem essa abordagem são RPM; pkg-utils; apt do Debian; e sistema Portage do Gentoo.
	Beyond Linux From Scratch 11.3/introduction_important_pkgmgt — English	User Based Management	User Based Management

• 1 / 2
  / 2