Skip to content

Instantly share code, notes, and snippets.

View ddunbar's full-sized avatar

Daniel Dunbar ddunbar

View GitHub Profile
@ddunbar
ddunbar / gist:c5058565691e0ec323d429994d77f9ba
Last active November 7, 2019 04:25
How I Configure My Kinesis
Enter Mac mode:
Hold =, press m.
The top four thumb keys while in Mac mode, from left to right are: Command | Option | Ctrl | Command
Enable Media keys:
Hold =, press n. If you have applied the remappings below, note that it is the *remapped* = (i.e. tab).
Disable key clicks:
Hold Progrm, press -/_ (disable beeps).
Hold Progrm, press |/\ (disable clicks).
@ddunbar
ddunbar / deployable-artifacts.md
Last active June 27, 2021 07:46
Deployable Artifacts thoughts

My hopes for deployable artifacts:

  1. Packages would be able to just describe how the things they build should get laid out in a tarball.
  2. We would implement this as part of the build, it should be super fast (we might want to consider actually generating the tar directly for portability & control purposes).
  3. Packages could have control over the permissions inside the tar file (ideally without having to manipulate the permissions in the filesystem, problematic sometimes if root permission in the tar is desired).
  4. The mechanism would support knowing how to handle RPATH issues.
  5. The mechanism would know how to handle libswift* portability issues.
  6. The mechanism would know how to handle cross-Linux distro issues.
  7. Unlike below, I wouldn't expect the mechanism to handle the GIT REVISION stuff, that belongs in a separate proposal.
  8. The mechanism would support typical Unix-y things, like bin, lib, libexec, share.
  9. The mechanism could support vendored assets like other DSOs or frameworks that can't l