14 How to configure a new architecture

• Create a new ports-arch user and group

• mkdir /var/portbuild/arch
  

• In that directory, for each branch that will be supported:

  mkdir branch
  

  
  
  

• Create a new zfs filesystem for backups:

  zfs create -o mountpoint=/a/portbuild/arch a/portbuild/arch
  

  
  
  

• Create a link for the webserver:

  ln -s /dumpster/pointyhat/arch/archive archive
  

  
  
  

• In the /var/portbuild/arch directory:

  mkdir clients
  

  
  
  

• Populate clients as usual

• mkdir loads
  

  
  
  

• ln ../make.conf ./make.conf
  

  
  
  

• create an empty mlist file

• (TBD if still neede?) create pnohang.arch

• create a fresh portbuild.conf file from one of the others

• create customized portbuild.machinename.conf files as appropriate

• cd .ssh && ssh-keygen
  

  
  
  

• Edit the .ssh/config file for convenience in using ssh

• Make the private configuration directory:

  mkdir /var/portbuild/conf/arch
  

  
  
  

• In that directory: create any dotunnel.* scripts needed

• Create a link for backups:

  mkdir /dumpster/pointyhat/arch/archive
  

  
  
  

• Tell qmanager about the arch:

  python /var/portbuild/evil/qmanager/qclient add_acl name=ports-arch uidlist=ports-arch gidlist=portmgr sense=1
  

  
  
  

• Edit /var/portbuild/scripts/buildenv

• Add the arch directory to /var/portbuild/scripts/zbackup and /var/portbuild/scripts/zexpire

• Kick-start the build for each branch with

  build create arch branch
  

  
  
  

• Only after the first time dopackages has been run: add the arch to /var/portbuild/scripts/dopackagestats