File: OSXReadme.md

package info (click to toggle)
pcp 4.3.2+really4.3.1-0.1
  • links: PTS
  • area: main
  • in suites: buster
  • size: 175,188 kB
  • sloc: ansic: 261,305; sh: 123,606; xml: 107,279; cpp: 72,127; perl: 18,283; python: 15,453; yacc: 8,249; lex: 2,585; makefile: 1,957; fortran: 60; java: 52
file content (28 lines) | stat: -rw-r--r-- 1,158 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
# OSX Vagrant boxes

There is an `osxsierra` Vagrant box defined, but it has some restrictions on use.
_Only_ if the underlying hardware is detected as Apple Mac and you've checked the licensing agreement is valid and explictly acknowledged this by touching a file.

The Vagrantfile will not allow launching the `osxsierra` box until you do.

Please read [the licensing agreement](http://images.apple.com/legal/sla/docs/macOS1012.pdf).

# #protips

* Getting the PCP build log from the guest.  First install this plugin:


    # will allow you to scp a file from the guest
    # very useful to grab the PCP build log
    vagrant plugin install vagrant-scp

  then you can grab the build log from the guest via:

     vagrant scp osxsierra:/vagrant/Logs/pcp .

# Caveats/Known Issues

* The first time you run `vagrant up osxsierra` you will get an `rsync` error. This can be safely ignored for now, just run `vagrant provision osxsierra` to continue past this.  Honestly the `rsync` error is probably a real issue, but there's more issues to battle through first..

# TODO
* During the `Makepkg` build of PCP there are errors occuring around `tar` failures.