|
|
Line 1: |
Line 1: |
| {{Person
| | On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that {{c|buildrepo}} has been configured to manage. The first number on each line is a '''failcount''', which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount: |
| |Geoloc=48.123028496893525, -1.671895980834961
| |
| |Location name=Rennes, Bretagne, France
| |
| |Full name=Antoine Pinsard
| |
| |Email=antoine.pinsard@gmail.com
| |
| |Nick=pytony | |
| }} | |
| | |
| == About Me ==
| |
| | |
| I am a 23 years old French developer. I am currently working as lead developer for a web start-up called ''Aladom'' (home services sector) in Rennes (Brittany, France). I started developing websites at the age of 11, which, bit by bit, led me to programming and GNU/Linux. I moved to Gentoo in 2010 and then Funtoo about three years later, in order to become the master of my computer and not the opposite. I am especially enthusiast about getting rid of features I don't need/use.
| |
| | |
| == How I met <del>your mother</del> Funtoo? ==
| |
| | |
| I don't remember.
| |
| | |
| == Why I stick to Funtoo? ==
| |
| | |
| In my childhood as a wee developer, I moved from distro to distro by curiosity, without understanding, fundamentally, the difference between them. This is the day I moved to Gentoo that I had a click. Well... the day... I must say the first time I booted on Gentoo Install CD, it was like "OK... Where are fancy windows and OK buttons... Am I really supposed to type some text here? Hmm... looks like this CD is buggy, let's try another distro.". But eventually I came to it again, and went through the famous handbook. I remember, It took the night to compile Gnome 3 and the nearly 200 "dependencies" and I had to wait until the early morning to get my fancy interface. A month later I had the feeling I had learn so much (and totally screwed up my system with my newbies commands) I had to reinstall Gentoo, and this time decided to build my own kernel thanks to kernel-seeds.org. Miraculously, it worked. Well... actually, I chose vanilla-sources, and as a total ignorant of what "vanilla" meant, I thought it would be a good idea to turn on {{c|USE<nowiki>=</nowiki>vanilla}} in {{c|/etc/make.conf}} to optimize packages for my kernel... No need to tell you it did not take a month to screw up my system. So I tried again, I loved it.
| |
| | |
| All of this is funny but this does not tell us why I moved to Funtoo and will stick to it.
| |
| | |
| == My Projects ==
| |
| | |
| * [https://github.com/apinsard/chuse chuse] - Portage tool to change USE flags and keep history of changes done
| |
| * [https://github.com/apinsard/Sapher-BT Sapher-BT] - A tiny bug tracker I developed to fit my needs as lead dev at Aladom
| |
| * [https://github.com/apinsard/Pi-Flavor Pi-Flavor] - OS from scratch in ARMv6 assembly for Raspberry Pi (sounds cool said like this, but actually it just blinks the ACT LED for now)
| |
| * [https://github.com/apinsard/mycfg-vim mycfg-vim] - My Vim configuration (If you want to get inspired or suggest me some stuff)
| |
| * [https://github.com/apinsard/mycfg-awesome mycfg-awesome] - My Awesome WM configuration (If you want to get inspired or suggest me some stuff)
| |
| * [https://github.com/apinsard/prettress-sm prettress-sm] - The project for which I actually only wrote the README
| |
| | |
| == Around the web ==
| |
| | |
| {{#widget:LinkedIn
| |
| |profile=http://www.linkedin.com/in/apinsard
| |
| |name=Antoine Pinsard
| |
| |norelated}}
| |
On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that buildrepo
has been configured to manage. The first number on each line is a failcount, which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount: