Changeset 1116 in ProjectBuilder for devel/website/about.shtml
- Timestamp:
- Nov 26, 2010, 12:54:34 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
devel/website/about.shtml
r1025 r1116 14 14 </div> 15 15 <p> 16 Project-Builder.org aka pb helps building continuously multiple OS packages from sources.16 We are strong proponents of the concept of Continuous Packaging. Project-Builder.org aka pb helps building continuously multiple OS packages from sources. 17 17 </p> 18 18 <p> 19 With the increasing role of FLOSS in enterprise , some development techniques linked to it also know a momentum. Continuous integration (shared sources repository, automatic build, automatic test) is such an example. The new process called continuous packaging should still be promoted and developed as best practice for industry.19 With the increasing role of FLOSS in enterprises, some development techniques linked to it also know a momentum. Continuous integration (shared sources repository, automatic build, automatic test) is such an example. The new process called Continuous Packaging should still be promoted and developed as best practice for industry. 20 20 </p> 21 21 <p> 22 Project-Builder.org is a new GPL v2 tool designed to help projects developers producing easily packages for multiple OS and architectures, on a regular basis, from a single source repository. 90% of users and admins prefer to install packages rather than tar files or content from a [D]VCS. But packages don't necessarily follow the development stream of projects, to package alpha, beta. Giving the possibility for projects to distribute seamlessly packages for whatever step of their development is clearly a gain for the whole community.22 Project-Builder.org is a new GPL v2 tool designed to help projects developers producing easily packages for multiple OS and architectures, on a regular basis, from a single source repository. 90% (from stats of sf.net) of users and admins prefer to install packages rather than tar files or content from a [D]VCS. But packages don't necessarily follow the development stream of projects, to package alpha, beta versions. Giving the possibility for projects to distribute seamlessly packages for whatever step of their development is clearly a gain for the whole community. 23 23 </p> 24 24 <p> … … 29 29 <li>- help new projects in the provisioning of packages (templates and skeletons for the various supported OS, generated structure, help in VM/VE build)</li> 30 30 <li>- Avoid code or metadata duplication, as well as has no impact on the original project (macro system, separate repository)</li> 31 <li>- Neutral in term of Unix environment (repository, system, package type 31 <li>- Neutral in term of Unix environment (repository, system, package type agnostic)</li> 32 32 </ul> 33 33 </p> 34 34 <p> 35 These features help reducing the development cost by providing a process, method and tools to realize continuous packaging during the whole project life cycle.35 These features help reducing the development cost by providing a process, methods and tools to realize continuous packaging during the whole project life cycle. 36 36 Today the tool supports: 37 37 <ul> 38 38 <li>- Muliple repository (none - aka tar balls, SVN, CVS, Git, Mercurial, SVK...)</li> 39 <li>- Multiple systems ((RPM Linux - Red Hat, SuSE, Mandriva, ..., deb Linux - Debian, Ubuntu, ..., ebuild -</li> 40 <li>Gentoo, pkg Solaris/OpenSolaris, ...)</li> 41 <li>- Multiple build environments (local, VM - QEMU, KVM, ..., VE - mock, rinse, pbuilder, ...)</li> 39 <li>- Multiple systems (RPM Linux - Red Hat, SuSE, Mandriva, ..., deb Linux - Debian, Ubuntu, ..., ebuild - Gentoo, pkg Solaris/OpenSolaris, ...)</li> 40 <li>- Multiple build environments (local, VM - QEMU, KVM, ..., VE - rpmbootstrap, mock, rinse, pbuilder, ...)</li> 42 41 <li>- Multiple repository manager (yum, urpmi, apt, ...)</li> 43 42 </ul> 44 and this at various phasis (development, test, integration, delivery)43 and this, at various phasis (development, test, integration, delivery). 45 44 </p> 46 45 <p> 47 It aims at becoming a tool sfor the <a href="http://vcs-pkg.org">vcs-pkg.org</a> initiative.48 It's today used for projects as diverse as FOSSology, MondoRescue, LinuxCOE, GOsa², itself, ...46 It aims at becoming a tool for the <a href="http://vcs-pkg.org">vcs-pkg.org</a> initiative. 47 It's today used for projects as diverse as <a href="http://www.fossology.org">FOSSology</a>, <a href="http://www.mondorescue.org">MondoRescue</a>, <a href="http://www.linuxcoe.org">LinuxCOE</a>, <a href="http://kde-apps.org/content/show.php/Meganizer?content=129907">Meganizer</a>, GOsa² (in study), itself, ... 49 48 50 49 … … 62 61 <P ALIGN=CENTER> 63 62 <I><B>Bruno Cornec</B></I><BR> 64 lead development, maintenance, documentation, web site, rpm packaging, Mandriva packaging</P>63 Lead development, maintenance, documentation, web site, rpm packaging, Mandriva packaging</P> 65 64 <P ALIGN=CENTER> 66 65 <I><B>Bryan Gartner</B></I><BR> 66 Ideas contributor, bug reporter</P> 67 <I><B>Joachim Langenbach</B></I><BR> 67 68 Ideas contributor, bug reporter</P> 68 69 <p></p> … … 71 72 </div> 72 73 <p><A NAME="old-devteam"></A>Who has been in the Project-Builder.org?</P> 73 <P ALIGN=CENTER>Nobody a has the project is too young for that ;-)</P>74 <P ALIGN=CENTER>Nobody as the project is too young for that ;-)</P> 74 75 <div class="h2-2"> 75 76 <h2>Artwork of this site</h2> … … 100 101 Project-Builder.org was first created because there was nothing like 101 102 it available at that time under a free license. Under the <a href="http://vcs-pkg.org">vcs-pkg.org</a> initiative, you may find other projects whose goals are aligned with those of Project-Builder.org. 102 Especially you should look at the <a href="https://build.opensuse.org/">OpenSUSE Build Service</a> .103 Especially you should look at the <a href="https://build.opensuse.org/">OpenSUSE Build Service</a> as another interesting build tool. 103 104 </P> 104 105 <P>
Note:
See TracChangeset
for help on using the changeset viewer.