Make Minor Modifications to a PBI Module

From PC-BSD Wiki
Revision as of 03:34, 29 January 2014 by Tigersharke (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search



NOTE: Translators should localize the following templates used:

This damn spiffy template enables a centralized Handbook Table of Contents which can be used in multiple ways. It calls an entirely automagical NavHeader template which uses the chronological relationship in the page names within the UseTOC template to choose the back and forward links. The same ordered list provides the Table Of Contents page links and provides for the flat_html page (although wiki page limits prevent this). It necessarily works within the versioned page system, which means that this template will need to be duplicated for each of the future versions.



{{UseTOC{{putVers}}|Nav}} invokes the NavHeader output similar to below:

But if the pages relating to the backward (left) or forward (right) icon/links are not yet defined by their translation, or if the page is not yet or no longer in the Table Of Contents then the result is as below:

Template loop detected: Template:UseTOC

Table Of Contents

{{UseTOC{{putVers}}|Toc}} invokes a formatted list of page links similar to below:
1. Introduction

1.1 Goals and Features
1.2 What's New in
1.3 PC-BSD® Releases
1.4 PC-BSD® for Linux Users


{{UseTOC{{putVers}}|flat}} causes the flat_html page output (but is limited by page size which makes it incomplete/broken in actual use).


How to insert new pages into the Table Of Contents
The previous section indicated that new PBI modules are uploaded to the PBI build server so that they can be built and tested. This section describes the two ways you can assist in testing PBIs.
Figure 11.5a: Viewing the Status of PBIs on the Build Server

Test PBIs Waiting for Approval

If you wish to help test a PBI before it has been approved, go to the build server[1] as shown in Figure 11.5a.

Find the name of the PBI you wish to test in the "Module" column and click its hyperlink. You can then download the file with the .pbi extension. Once downloaded, run pbi_add /path/to/pbi to install the PBI. If you find any problems with the PBI, send an email to the PBI-dev[2] mailing list describing how to recreate the problem. Include the text of any error messages you receive.

Investigate or Fix a Failed Build

You can try to resolve PBI modules that have a "Build Status" of "FAILED". If you click on the name of a failed module, you can download the file named last_100.log for that module. This file is in ASCII text so it can be viewed in any text editor.

If you think you know the cause of the problem after reading the error messages, you can review the PBI's module by clicking its "git" hyperlink. If you decide to copy/paste a file in order to edit it locally, click the "Raw" link for the file.

If you make an edit to correct the problem, send the modified file (or a diff) to the PBI-dev[2] mailing list so the changes can be uploaded to the build server.


  2. 2.0 2.1
Other languages:German 0% • ‎English 100%
Personal tools