projects / pakfire.git / blame
| Commit | Line | Data |
|---|---|---|
| 0289776a MT |
1 | ############################################################################### |
| 2 | # # | |
| 3 | # Pakfire - The IPFire package management system # | |
| 4 | # Copyright (C) 2011 Pakfire development team # | |
| 5 | # # | |
| 6 | # This program is free software: you can redistribute it and/or modify # | |
| 7 | # it under the terms of the GNU General Public License as published by # | |
| 8 | # the Free Software Foundation, either version 3 of the License, or # | |
| 9 | # (at your option) any later version. # | |
| 10 | # # | |
| 11 | # This program is distributed in the hope that it will be useful, # | |
| 12 | # but WITHOUT ANY WARRANTY; without even the implied warranty of # | |
| 13 | # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # | |
| 14 | # GNU General Public License for more details. # | |
| 15 | # # | |
| 16 | # You should have received a copy of the GNU General Public License # | |
| 17 | # along with this program. If not, see <http://www.gnu.org/licenses/>. # | |
| 18 | # # | |
| 19 | ############################################################################### | |
| 20 | ||
| 21 | Pakfire is the package management system of the IPFire (http://www.ipfire.org) | |
| 22 | firewall distribution. | |
| 23 | ||
| 24 | It is as well the buildsystem that is used to create the distribution. | |
| 25 | ||
| 26 | Development goals have been: | |
| 27 | ||
| 28 | * To be very fast | |
| 29 | As system administration and package development is a daily job and needs | |
| 30 | to be done very frequently, it needs to be fast and reliable. | |
| 31 | Pakfire is trying to reach this goal by having a very light package format | |
| 32 | and a very fast dependency solver that is using the SAT algorithm | |
| 33 | originally developed by SuSE. | |
| 34 | ||
| 35 | * One error should not break the whole distribution | |
| 36 | Recently, if one or more packages had a build error, there was no way to | |
| 37 | skip that. Pakfire 3 divides the whole distribution into lots of little | |
| 2045f0e9 | 38 | packages, which are versioned. So if one package does not build, you |
| 0289776a MT |
39 | can just use the older version and do what you were doing. The error |
| 40 | can be fixed later. | |
| 41 | ||
| 42 | * Multiple architectures and distributions | |
| 43 | The buildsystem should be able to work on other distributions as well, so | |
| 44 | the developers do not need to set up a specific development system. You | |
| 45 | can now use every common distribution like Fedora, install Pakfire on it | |
| 46 | and start with your work. Additionally, pakfire is able to build ix86 | |
| 47 | architectures on an x64_86 machine. | |
| 48 | ||
| 49 | * Support multiple repositories | |
| 50 | Pakfire should be able to support multiple repositories. Which can be | |
| 51 | a testing repository, unstable, stable or a repository for development | |
| 52 | of a new feature. | |
| 53 | ||
| 54 | In the end, pakfire turned out to be exactly what the IPFire developers wanted. | |
| 55 | It is fast and easy to use, you can start development after only one minute | |
| 56 | of installation of the software. No more waiting for the compiler to finish | |
| 57 | compiling the whole distribution. | |
| 58 | ||
| 59 | - The Pakfire development team | |
| 60 | ||
| 61 | Michael Tremer <michael.tremer@ipfire.org> | |
| 62 | Arne Fitzenreiter <arne.fitzenreiter@ipfire.org> | |
| 63 | Christian Schmidt <christian.schmidt@ipfire.org> | |
| 64 | Stefan Schantl <stefan.schantl@ipfire.org> | |
| 65 | ||
| 66 | Please report all bugs to: http://redmine.ipfire.org/projects/pakfire3 |