Changes between Version 4 and Version 5 of Bootstrapping


Ignore:
Timestamp:
Apr 11, 2020, 1:15:08 AM (4 years ago)
Author:
Bruno Cornec
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Bootstrapping

    v4 v5  
    1111  * On the platform in use, you have the requisite tools to create a native package
    1212
    13 In this example, lets assume you are using a Debian Lenny amd64 system (presumably before this becomes the stable Debian release)
     13In this example, lets assume you are using a Debian amd64 system
    1414
    1515== Setup ==
    1616
    1717  * Certainly the easiest way to get started is to grab the nearest equivalent format already available for project-builder.org deliverables (so, continuing the example cited above, [ftp://ftp.project-builder.org/ grab] the lastest stable release source files):
    18     * in the debian 4.0 subdirectories -- libprojectbuilder-perl_<version>.tar.gz and project-builder_<version>.tar.gz
     18    * in the debian x.0 subdirectories -- libprojectbuilder-perl_<version>.tar.gz and project-builder_<version>.tar.gz
    1919  * Since these were generated with project-builder.org (likely via the cms2build or beyond), you can safely assume that they contain not only the source code for project-builder.org, but also the necessary packaging information itself, for the selected platform
    2020  * In this example, one can extract the source files, enter the resulting directory, and run the typical packaging commands locally to generate installable packages
    … …  
    2929
    3030  * for the user (which really should not be root) intending to use project-builder.org (and to build subsequent packages), you must create a simple configuration file
    31     * create '''~/.pbrc''' with at least the following contents ('''NOTE:''' ''yes, we should supply such a template with future releases''. In the mean time, have a look at this [http://trac.project-builder.org/browser/projects/pb/.pbrc example])
     31    * create '''~/.pbrc.yml''' with at least the following contents ('''NOTE:''' ''yes, we should supply such a template with future releases''. In the mean time, have a look at this [http://trac.project-builder.org/browser/projects/pb/.pbrc.yml example])
    3232
    3333{{{
    3434# how to get project-builder.org source
    35 pburl pb = svn://svn.project-builder.org/mondo/svn/pb
     35pburl:
     36  pb: svn://svn.project-builder.org/mondo/svn/pb
    3637
    3738# where to get the packaging templates
    38 pbconfurl pb = svn://svn.project-builder.org/mondo/svn/pb/pbconf
     39pbconfurl:
     40  pb: svn://svn.project-builder.org/mondo/svn/pb/pbconf
    3941
    4042# local prefix for sandbox checkouts and local build artifacts
    41 pbdefdir default = $ENV{'HOME'}/pb/projects
    42 pbdefdir pb = $ENV{'HOME'}
    43 pbconfdir pb = $ENV{'HOME'}/pb/pbconf
     43pbdefdir:
     44  default: $ENV{'HOME'}/pb/projects
     45pbdefdir:
     46  pb: $ENV{'HOME'}
     47pbconfdir:
     48  pb: $ENV{'HOME'}/pb/pbconf
    4449
    4550# location of Virtual Machine infrastructure
    46 vmpath default = /home/qemu
     51vmpath:
     52  default: /home/qemu
    4753
    4854# location of Virtual Environment (chroot) infrastructure
    49 vepath default = /home/mock
     55vepath:
     56  default: /home/mock
    5057}}}
    5158
    52   ('''NOTE:''' ''the above examples will only work after anonymous svn access to project-builder.org is enabled'')
    53 
    5459  * regardless of the type of virtualization you will later employ (lets assume Virtual Machines via qemu), in the directory of '''vmpath''' from the previous configuration file
    55     * create '''.pbrc''' with at least the following contents (NOTE: an upstream example is also provided for [http://trac.project-builder.org/browser/projects/qemu/.pbrc qemu/kvm] and [http://trac.project-builder.org/browser/projects/rinse/pbconf/devel/conf/.pbrc rinse])
     60    * create '''.pbrc.yml''' with at least the following contents (NOTE: an upstream example is also provided for [http://trac.project-builder.org/browser/projects/qemu/.pbrc.yml qemu/kvm] and [http://trac.project-builder.org/browser/pb/devel/rpmbootstrap/etc/.pbrc.yml docker])
    5661
    5762{{{
    5863# type of VM
    59 vmtype default = qemu
     64vmtype:
     65  default: qemu
    6066
    6167# VM instance configuration
    62 vmntp default = pool.ntp.org
    63 vmhost default = localhost
    64 vmlogin default = pb
    65 vmport default = 2222
    66 vmtmout default = 120
    67 vmopt default = -m 384 -daemonize
    68 vmsize default = 5G
     68vmntp:
     69  default: pool.ntp.org
     70vmhost:
     71  default: localhost
     72vmlogin:
     73  default: pb
     74vmport:
     75  default: 2222
     76vmtmout:
     77  default: 120
     78vmopt:
     79  default: -m 384 -daemonize
     80vmsize:
     81  default: 5G
    6982
    7083# a comma seperated list of all the desired tuples (distro-ver-arch)
    71 vmlist default = mandriva-2008.1-i386,fedora-9-i386,rhel-2.1-i386,rhel-3-i386,rhel-4-i386,rhel-5-i386,opensuse-11.0-i386,sles-10-i386,gentoo-nover-i386,debian-4.0-i386,ubuntu-8.10-i386,debian-lenny-x86_64
     84vmlist:
     85  default: mageia-7-x86_64,fedora-30-x86_64,rhel-4-i386,rhel-5-i386,opensuse-15-x86_64,sles-10-i386,gentoo-nover-i386,debian-4.0-i386,ubuntu-8.10-i386
    7286}}}
    7387
    … …  
    7993Okay, so with much anticipation, you are now ready to build new packages for your local host
    8094
    81   * as the designated user (with the ~/.pbrc) start slowly, grabbing CMS versions of project-builder.org and prepping the build
     95  * as the designated user (with the ~/.pbrc.yml) start slowly, grabbing CMS versions of project-builder.org and prepping the build
    8296
    8397{{{