toraritte

Yes, there are several ways to do this, but none of them are as direct and simple as git v2.1.2; htop v1.2.3 and come with a lot of caveats.

aside
Specifying versions for programming language packages are possible too, but that topic seems to be even messier. The most promising standardization effort to date is [dream2nix][1].

0. Methods

That is, available at the time of this writing:

0.1 "versioned" attribute paths (if available)

CMCDragonkai

Shebang Scripts in Nix Derivations

When you create a derivation, and you later run nix-build on the Nix derivation. Nix will transport the source to a chrooted temporary build directory (this actually can be configured in NixOS configuration.nix). The reason to do this is to ensure deterministic builds in a clean environment.

However the environment is so clean that no dependencies that you don't explicitly declare will be available in that environment. Also things that you take for granted like PATH is something that needs to be explicitly built.

mik30s

#include <iostream>
#include <stdio.h>
#include <stdlib.h>
#include <linux/ioctl.h>
#include <linux/types.h>
#include <linux/v4l2-common.h>
#include <linux/v4l2-controls.h>
#include <linux/videodev2.h>
#include <fcntl.h>
#include <unistd.h>

Two9A

<?php
/**
 * Dirty, dirty Reddit bot: Decronym
 */

class Reddit {
    const USERNAME = 'Decronym';
    const PASSWORD = '***';
    const CLIENTID = '***';
    const SECRET   = '***';

bzerangue

Verify and Repair Disk Permissions via Terminal (Mac OS X)

Verify Permissions

diskutil verifyPermissions /

Repair Permissions

diskutil repairPermissions /

DanHerbert

OBSOLETE

This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.

I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.

Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.

walling

'use strict';

var defaultColors = [ '#000', '#D00', '#00CF12', '#C2CB00', '#3100CA',
	'#E100C6', '#00CBCB', '#C7C7C7', '#686868', '#FF5959', '#00FF6B',
	'#FAFF5C', '#775AFF', '#FF47FE', '#0FF', '#FFF' ];

function term2html(text, options) {
	options = options || {};
	var colors = options.colors || defaultColors;

oxling

% This version doesn't work.
min_wrong([Item], Item).
min_wrong([Item | List], Item) :- 
	min_wrong(List, List_Answer),
	Item =< List_Answer.
min_wrong([_Item | List], Answer) :-
	min_wrong(List, Answer).

% Output:
%