nixpkgs/pkgs/servers/ssh-script/builder.sh

source $stdenv/setup

ensureDir $out

sed -e "s^@bash\@^$bash^g" \
    -e "s^@sshd\@^$ssh^g" \
    -e "s^@initscripts\@^$initscripts^g" \
    -e "s^@coreutils\@^$coreutils^g" \
    -e "s^@softdeps\@^$softdeps^g" \
    < $script > $out/$nicename

chmod +x $out/$nicename
WiP version for ssh stop/start script, far from finished svn path=/nixpkgs/trunk/; revision=4369 2005-12-15 00:35:02 +01:00			`source $stdenv/setup`

and also, don't forget to actually make $out first... svn path=/nixpkgs/trunk/; revision=4409 2005-12-22 17:05:03 +01:00			`ensureDir $out`

WiP version for ssh stop/start script, far from finished svn path=/nixpkgs/trunk/; revision=4369 2005-12-15 00:35:02 +01:00			`sed -e "s^@bash\@^$bash^g" \`
pass around the right parameters...d'oh svn path=/nixpkgs/trunk/; revision=4408 2005-12-22 17:03:29 +01:00			`-e "s^@sshd\@^$ssh^g" \`
			`-e "s^@initscripts\@^$initscripts^g" \`
we depend on coreutils (chmod, etc.) svn path=/nixpkgs/trunk/; revision=4410 2005-12-22 19:10:47 +01:00			`-e "s^@coreutils\@^$coreutils^g" \`
some small changes...probably the way it is done now (declaring the dependencies, such as "networking" in Nix expressions) is not entirely right, at least, trying to start them from for example this SSH script is not the right way. A cleaner solution is being developed :) svn path=/nixpkgs/trunk/; revision=5034 2006-03-14 14:44:28 +01:00			`-e "s^@softdeps\@^$softdeps^g" \`
more script work. Now what we need is: * generic functions to register with the system, good for "weak dependencies" svn path=/nixpkgs/trunk/; revision=5009 2006-03-08 20:38:12 +01:00			`< $script > $out/$nicename`
we need to the path to initscripts and also make it executable svn path=/nixpkgs/trunk/; revision=4411 2005-12-22 19:16:10 +01:00
more script work. Now what we need is: * generic functions to register with the system, good for "weak dependencies" svn path=/nixpkgs/trunk/; revision=5009 2006-03-08 20:38:12 +01:00			`chmod +x $out/$nicename`