Skip to content

Instantly share code, notes, and snippets.

View rogeriopradoj's full-sized avatar
😀

Rogerio Prado de Jesus rogeriopradoj

😀
View GitHub Profile
@rogeriopradoj
rogeriopradoj / 1.sh
Created July 8, 2014 10:07
update flash os x, error message safari is open
ps -ax | grep WebKitPluginHost
kill -9 1234
#!/bin/bash
mkdir /tmp/curl-ca-bundle
cd /tmp/curl-ca-bundle
wget http://curl.haxx.se/download/curl-7.22.0.tar.bz2
tar xzf curl-7.22.0.tar.bz2
cd curl-7.22.0/lib/
./mk-ca-bundle.pl
if [ ! -d /usr/share/curl/ ]; then
sudo mkdir -p /usr/share/curl/
else
@rogeriopradoj
rogeriopradoj / README.md
Last active August 29, 2015 14:05
utf8.php

Transform textfiles from any encoding type to utf8

wget -O utf8.php http://goo.gl/QrblHb
chmod +x utf8.php
./utf8.php

Example, for all srt in a folder:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.kitematic.route</string>
<key>ProgramArguments</key>
<array>
<string>bash</string>
<string>-c</string>

Deploying Sculpin Sites to GitHub Pages

I wanted to be able to use Sculpin to generate GitHub pages. Here's what I did...

  1. Created a super awesome Sculpin site from the Sculpin Blog Skeleton

  2. Make sure everything is under version control in my master branch (except things that shouldn't be. see the .gitignore)

  3. Updated publish.sh:

#!/bin/bash

# install
update-rc.d btsyncd defaults

# uninstall
/etc/init.d/btsyncd stop
rm -rf /etc/init.d/btsyncd
rm -rf /DataVolume/cache/btsync/

update-rc.d -f btsync remove
$ curl -qsILf http://git.php.net/\?p\=web/php-distributions.git\;a\=blob\;f\=php-5.5.3.tar.bz2\;h\=2f8f088ff89cb77873798a58027dcf68271f4cda\;hb\=4c39e3c8edc074dc80077a00eab518be309a858d | grep -o -E 'filename=.*$' | sed -e 's/filename=//' -e 's/\"//g' | tr -d '\r\n' > curl.txt
$ wget -q --server-response --spider http://git.php.net/\?p\=web/php-distributions.git\;a\=blob\;f\=php-5.5.3.tar.bz2\;h\=2f8f088ff89cb77873798a58027dcf68271f4cda\;hb\=4c39e3c8edc074dc80077a00eab518be309a858d 2>&1 | grep -o -E 'filename=.*$' | sed -e 's/filename=//' -e 's/\"//g' | tr -d '\r\n' > wget.txt
@rogeriopradoj
rogeriopradoj / 1.md
Created October 29, 2014 12:41
php-build mac os x mcrypt boxen homebrew
time CONFIGURE_OPTS="--with-mcrypt=/opt/boxen/homebrew/opt/mcrypt" php-build -i development --pear 5.5.4 ~/.phpenv/versions/5.5.4 ; say php-build acabou

Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.

For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.

But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.

SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil

Index: pt_BR/appendices/comparisons.xml
===================================================================
--- pt_BR/appendices/comparisons.xml (revision 335264)
+++ pt_BR/appendices/comparisons.xml (working copy)
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="utf-8"?>
-<!-- EN-Revision: 311459 Maintainer: fibbarth Status: ready -->
-<!-- CREDITS: narigone -->
+<!-- EN-Revision: 331317 Maintainer: fibbarth Status: ready -->
+<!-- CREDITS: narigone, Nawarian Níckolas -->