Processes for building Porteus packages.: Difference between revisions
From HacDC Wiki
(Created page with "==From Slackbuild== * Download the SlackBuild tarball (from [http://slackbuilds.org/ slackbuilds.org], for example). It will contain a .SlackBuild script (which is basically a s...") |
|||
Line 20: | Line 20: | ||
==Making Porteus modules available to Byzantium developers== | ==Making Porteus modules available to Byzantium developers== | ||
* Copy it off of your virtual machine or USB key. | * Copy it off of your virtual machine or USB key. | ||
* Check it into | * Check it into the [http://svn.virtadpt.net/byzantium/ Subversion repository]. Do NOT check Porteus packages into Git! | ||
Revision as of 20:44, 7 August 2011
From Slackbuild
- Download the SlackBuild tarball (from slackbuilds.org, for example). It will contain a .SlackBuild script (which is basically a shell script that does the compiling for you) as well as whatever other files will be required by the package.
- Uncompress the tarball to a temporary directory.
- Use wget to download the source code archive referenced by the .info script (in the DOWNLOAD line).
- If necessary, edit the variables in the .SlackBuild script to bring it up up to date.
- Run the .SlackBuild script as the root user. This is important for the package creation process because it allows, among other things, file ownerships and permissions to be set properly.
- If the .SlackBuild worked, a Slackware package file will be found in /tmp. Use `ls -ltr /tmp` to find it.
- Convert the .tgz or .txz Slackware package into a Porteus module
- tgz2xzm /path/to/slackware.tgz /path/to/porteus.xzm
- txz2xzm /path/to/slackware.txz /path/to/porteus.xzm
Manually
Used for packages that do not have slackbuild files associated with them.
Activating Porteus modules
- Move the .xzm file to your porteus/modules directory (in my VM the full path is /mnt/sda1/porteus/modules, but yours may vary).
- Run the command `activate /path/to/porteus/modules/newmodules.xzm` as the root user. If it worked you will see a window pop up (if you're using the desktop) confirming activation.
- Once activated, modules remain active across reboots (if Porteus is installed to read-write media).
Making Porteus modules available to Byzantium developers
- Copy it off of your virtual machine or USB key.
- Check it into the Subversion repository. Do NOT check Porteus packages into Git!