- Install Puppet from MSI
- Note that the Ruby install path is something like
c:\program files\puppet labs\puppet\sys\ruby
- Install Chocolatey in PowerShell with
iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))
- Close / re-open PowerShell
- Install Ruby Devkit -
choco install ruby2.devkit
- Add Ruby to the beginning of the PATH using an 8.3 style path -
$Env:PATH = "C:\Progra~1\Puppet~1\Puppet\sys\ruby\bin;" + $Env:PATH
(NOTE:dir /x
insidecmd.exe
can be helpful to find 8.3 style paths)- If done correctly
gem env
should contain a line withRUBY EXECUTABLE: C:/PROGRA~1/PUPPET~1/Puppet/sys/ruby/bin/ruby.exe
- This part is absolutely critical, so if
gem env
doesn't have a bunch of 8.3 style paths, you've done something wrong
- If done correctly
- Configure DevKit for use with our vendored Ruby
cd \DevKit-2.0-x64
#!/bin/bash | |
# | |
# Set up OSX preferences | |
# | |
# Inspired by: https://github.com/mathiasbynens/dotfiles/blob/master/.osx | |
########################################### | |
# CONFIG | |
HOSTNAME="machiavellia" | |
TIMEZONE="America/Chicago" # 'systemsetup -listtimezones' |
A DMG Installer is convenient way to provide end-users a simple way to install an application bundle. They are basically a folder with a shortcut to the Applications directory but they can be customized with icons, backgrounds, and layout properties. A DMG file (.dmg) is a Mac OS X Disk Image file and it is used to package files or folders providing compression, encryption, and read-only to the package.
##Creating the DMG file #Disk Utility
Parsed from the Roslyn source code using Roslyn.
Code | Severity | Message |
---|---|---|
CS0006 | Error | Metadata file '{0}' could not be found |
CS0009 | Fatal | Metadata file '{0}' could not be opened -- {1} |
CS0012 | Error | The type '{0}' is defined in an assembly that is not referenced. You must add a reference to assembly '{1}'. |
CS0016 | Error | Could not write to output file '{0}' -- '{1}' |
sdkVersion="6.0.100" | |
sudo rm -rf /usr/local/share/dotnet/sdk/$sdkVersion | |
sudo rm -rf /usr/local/share/dotnet/sdk-manifests/$sdkVersion |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j