Aller au contenu

« PC-BSD Installer » : différence entre les versions

Un article de Wikipédia, l'encyclopédie libre.
Contenu supprimé Contenu ajouté
Aucun résumé des modifications
Aucun résumé des modifications
Ligne 3 : Ligne 3 :
* article a compléter en s'appuyant sur http://www.pcbsd.org/promotion/ThePBIMethod.pdf. ;)
* article a compléter en s'appuyant sur http://www.pcbsd.org/promotion/ThePBIMethod.pdf. ;)
* article lié à [[PC-BSD]]
* article lié à [[PC-BSD]]

Une des caractéristiques principales de la distribution PC-BSD est sont système de paquetage: les PBI.

Traditionnellement dans les paquetages des systèmes d'exploitation opensource, les programmes sont dépendants de multiples autres petits programmes (appelés librairies) pour fonctionner. Parfois même, certains programmes ont chacun besoin de versions différentes de la même librairie pour fonctionner.
The PBI Method
One of the most important features of PC-BSD is its package
management system. One of the biggest complaints we hear on other open
source systems is how difficult it is to install new software. This often has nothing
to do with the quality of the tools provided for installation, but rather with the
methodology behind the software management itself. For example:
Traditional Packages PC-BSD PBI’s
In a traditional open source packaging system, programs are dependant
upon many smaller programs (libraries) to function. More often than not, similar
programs will be dependant upon different versions of the same libraries to run.
This can create a tangled web of dependencies which must be satisfied in order
for all your software to function. What happens when you want to upgrade one of
your programs, and it requires a newer library? Often upgrading one library
requires that some other software dependant upon it must be updated as well. If
an updated version of the other software is not available, the user may be stuck
with not installing the new package, or figuring out how to compile the broken
packages from their original source code. This resulting hassle from package
installation can lead to even more experienced users throwing up their hands in
defeat.
PC-BSD has seen the problems this packaging system has created, and
has instead opted for a different approach. Instead of a tangled web of
dependencies on each system, our PBI files are created to be as self-contained
as possible. Each program will include the various libraries and programs
necessary for operation. From the developer’s standpoint, this just requires one
extra step of making sure that your PBI file contains the files necessary for your
program’s operation, but for end users the process is seamless. Packages can
be added and removed at will, without any fear of breaking other software
installed on the system.
Copyright 2006 – PC-BSD Software
www.pcbsd.com
Pkg A Pkg B
Pkg A
Pkg B

Version du 2 mai 2006 à 11:32

ou PBI.

Une des caractéristiques principales de la distribution PC-BSD est sont système de paquetage: les PBI.

Traditionnellement dans les paquetages des systèmes d'exploitation opensource, les programmes sont dépendants de multiples autres petits programmes (appelés librairies) pour fonctionner. Parfois même, certains programmes ont chacun besoin de versions différentes de la même librairie pour fonctionner. The PBI Method One of the most important features of PC-BSD is its package management system. One of the biggest complaints we hear on other open source systems is how difficult it is to install new software. This often has nothing to do with the quality of the tools provided for installation, but rather with the methodology behind the software management itself. For example: Traditional Packages PC-BSD PBI’s In a traditional open source packaging system, programs are dependant upon many smaller programs (libraries) to function. More often than not, similar programs will be dependant upon different versions of the same libraries to run. This can create a tangled web of dependencies which must be satisfied in order for all your software to function. What happens when you want to upgrade one of your programs, and it requires a newer library? Often upgrading one library requires that some other software dependant upon it must be updated as well. If an updated version of the other software is not available, the user may be stuck with not installing the new package, or figuring out how to compile the broken packages from their original source code. This resulting hassle from package installation can lead to even more experienced users throwing up their hands in defeat. PC-BSD has seen the problems this packaging system has created, and has instead opted for a different approach. Instead of a tangled web of dependencies on each system, our PBI files are created to be as self-contained as possible. Each program will include the various libraries and programs necessary for operation. From the developer’s standpoint, this just requires one extra step of making sure that your PBI file contains the files necessary for your program’s operation, but for end users the process is seamless. Packages can be added and removed at will, without any fear of breaking other software installed on the system. Copyright 2006 – PC-BSD Software www.pcbsd.com Pkg A Pkg B Pkg A Pkg B