This page will be re-written in the future, for now it's here as-is being copy-pasted from several sources.
NB: All the shell stuff assumes you are running bash. If you are using sh or ksh, you will need to manually expand the brace expansions and if you are using csh or tcsh, you will need to adjust the for-loops and brace expansions for that shell. To make a SysV pkg from a cpio file: 1. Make a temp/working directory 2. In the temp/working dir, blow up the cpio file (as root, or with sudo if you have that installed): cpio -idmv /path/to/foo.cpio 2b. If the cpio file was already installed, an alternative to expanding the cpio file again is to pipe the output of 'cpio -cit < foo.cpio' to 'pkgproto' to build the prototype file in the next step, but it is not as easy to search for symlinks using this method. 3. Build the pkg prototype file (does not have to be done as root): echo 'i pkginfo' > prototype pkgproto {dirs,created,from,cpio} >> prototype 3a. This is the tricky part. If there are any symbolic links in the pkg, for some reason, the pkgproto for AMIX doesn't include them in the prototype file, so, we have to add them manually. You'll need the coreutils package installed to get the 'readlink' command. The following example just searches the 'usr' subdirectory, but if the pkg installs stuff outside of 'usr', then they will need to be searched/accounted for as well: find usr -type l -print > one for i in `cat one` ; do readlink -f $i ; done | sed -e "s|`pwd`||" -e "s|^/||" > two paste -d= one two | awk '{print "s none", $1}' >> prototype The 'one' and 'two' files can be removed after the 'paste' command. 3b. At this point, it's not a bad idea to check the prototype file for any inconsistancies with regards to permissions and file ownership. For the most part, everything should probably be 'root root', or maybe 'bin bin', but there are exceptions. 4. Create a pkginfo file. The 'PKG' name can only be up to 9 characters long. PKG=pkgname ARCH=m68k NAME=My nifty package VERSION=1.2.3 CATEGORY=utilities 5. Make the package structure: pkgmk -d `pwd` -r / 6. Bundle it up into a package file: pkgtrans -s `pwd` /path/you/store/pkgs/pkgname-1.2.3.pkg 7. To install your new pkg (as root, or with sudo): pkgadd -d /path/you/store/pkgs/pkgname-1.2.3.pkg --- If you configure/install packages to install to their own directory (/usr/local/pkgname, /opt/AmixBP/pkgname, etc), then you can build your prototype file with something like: cd / ; find usr/local/pkgname | pkgproto >> /path/to/working/dir/prototype ; cd - as the command step of 3 above. Just keep an eye out for bits that might have been installed elsewhere, like gcc likes to put the man pages in /usr/man/* regardless of the --prefix supplied during the configure step. If you just install everything to /usr/local, which makes it easier on the PATH, I use 'find' to look for files newer than the Makfile for the package that was just installed: cd / ; find usr -newer ~/dl/foo-2.04/Makefile | pkgproto >> /path/to/working/dir/prototype The prototype file will need a little cleaning, make sure that there are entries for all directories: i pkginfo d none usr 0755 root root d none usr/local 0755 root root d none usr/local/bin 0755 root root The above 'find' command will probably only find /usr/local/bin, you'll need to manually add the two directory entries above it. Also, check lower in the file for other examples, like '/usr/local/man/man1' (for man pages), might need to add an entry for '/usr/local/man', etc. If you miss any, 'pkgmk' will let you know. Just fix them, then re-run pkgmk, adding the '-o' flag to 'overwrite' the previous run.
More information on AmixBP (backports for Amix, not updated since 2009).
After downloading the desired files from sourceforge.net, to unpack them into the default location /opt/amixbp on your Amiga UNIX machine run the following command:
zoo xpq filename.tar.zoo | gtar -xvC / -f -
This will unpack the files to the correct location. If you'd rather not unpack straight into /opt/amixbp, you can unpack to your current directory by omitting the “C /” from the gtar options. This will create an opt/amixbp directory tree descending from your pwd. When unpacking the files, don't worry about errors regarding existing directories. This is normal.
You need to add /opt/amixbp/bin to your path. If you would like files installed to take precedence over the native utilities, add it to the front of your path. If you want to Amiga UNIX commands and utilities to take precedence, add it to the back of your path. In that case, to force the use of AmixBP software (for example: Amiga UNIX provides an old gcc, but so does AmixBP) you will need to specify the full path. ie: /opt/amixbp/bin/gcc
Installing the software is fairly simple. You will need bzip2 to handle the archives, this is provided here for the binary only. If you like, you can download the full bzip2 archive from the file galleries, which requires bzip2 to extract. To install the bzip2.Z file, as root do:
uncompress bzip2.Z chmod a+x bzip2 cp -p bzip2 /usr/bin
Now you have bzip2. To install any of the cpio.bz2 archives, become root (su), cd to / and do:
bzip2 -dc filename.cpio.bz2 | cpio -ivcdm
If you have the bzip2 archive installed, you can use bzcat instead of bzip2 -dc.
If you don't entirely trust the cpio archives, you can install them into a fake root tree and move the files later. For example, you can make a directory in /tmp, unarchive the file there, check it out, and move the directories out to / when you're satisfied.
Note that most archives will unpack to /usr/local, so you need to add directories like /usr/local/bin and /usr/local/sbin to your path if you want to execute them without explicitly specifying the location of the files (ie: instead of make you would have to do /usr/local/bin/make if /usr/local/bin is not in your path).
SUCCESS
FAILS
IN PROCESS
CHANGES NEEDED changes needed for successful compilation on AMIX
WANT-TO-BUILD
ANY modern window manager for X — Please