22 | | which means that here I named my project for netperf for Project-Builder (I can choose what I want but need to be consistent everywhere). |
23 | | |
24 | | Then get the bits of the project you want to package. It could be using a SVN or CVS access if there is such a thing, or by downloading (at worse) the tar file of the project. Then extract that under a newly created directory that you referenced in your project configuration file: |
25 | | |
26 | | {{{ |
27 | | $ cd /tmp |
28 | | $ wget ftp://ftp.netperf.org/netperf/netperf-2.4.4.tar.bz2 |
29 | | $ mkdir -p $HOME/netperf/src |
30 | | $ cd $HOME/netperf/src |
31 | | $ umask 022 |
32 | | $ tar xvfj /tmp/netperf-2.4.4.tar.bz2 |
33 | | $ rm -f /tmp/netperf-2.4.4.tar.bz2 |
34 | | }}} |
| 29 | which means that here I named my project netperf for Project-Builder (I can choose what I want but need to be consistent everywhere). Also that configuration file is linked to the person who wants to package the software. Another configuration file will also be used, which only concerns the project itself. |
| 30 | |
| 31 | The pbconfurl keyword indicates where are stored the configuration files for pb allowing us to build netperf packages with them. |
| 32 | Here by default, everything will be extracted under $ENV{'HOME'}/project-builder for all projects we decide to package. Other keywords exist and may be used, but won't be needed for such a simple project. |
| 33 | |
| 34 | To get the bits of the project you want to package, different protocols may be used. Currently supported protocols are using a SVN or CVS access if there is such a thing, or URL pointing to a ftp or http server. |
38 | | You will now need to get the latest and greatest project-builder software from our [ftp://ftp.project-builder.org ftp] repository. Of course we provide lots of packages for your distribution ;-) Or a tar.gz file if you prefer. Once available, you can use the newproj option of pb to create the infrastructure that is mandatory for pb. It is mandatory that there is a corespondance between the directory mentioned in $HOME/.pbrc and the -r option: |
39 | | |
40 | | {{{ |
41 | | $ pb -p netperf -r `pwd` newproj |
42 | | Creating /users/bruno/netperf/src/pbconf directory |
43 | | |
44 | | Do not to forget to commit the pbconf directory in your CMS if needed |
45 | | After having renamed the pkg1 directory to your package's name |
46 | | |
47 | | Project: netperf |
48 | | Action: newproj |
| 38 | You will now need to get the latest and greatest project-builder software from our [ftp://ftp.project-builder.org ftp] repository. Of course we provide lots of packages for your distribution ;-) Or a tar.gz file if you prefer. Once available, you can use the newproj option of pb to create the infrastructure that is mandatory for pb. The latest version available of netperf at the time of this writing is 2.4.4. |
| 39 | |
| 40 | {{{ |
| 41 | $ pb -p netperf -r 2.4.4 newproj |