<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Binpkg on BAFM</title><link>https://christian.blog.pakiheim.de/tags/binpkg/</link><description>Recent content in Binpkg on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Sat, 16 Aug 2014 10:12:40 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/binpkg/index.xml" rel="self" type="application/rss+xml"/><item><title>Turning a simple chroot into a binpkg repository</title><link>https://christian.blog.pakiheim.de/posts/2014-08-16_turning-a-simple-chroot-into-a-binpkg-repository/</link><pubDate>Sat, 16 Aug 2014 10:12:40 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/2007/10/12/turning-a-simple-chroot-into-a-binpkg-repository/</guid><description>&lt;p&gt;OK, since Alex asked me last Sunday what exactly needs to be done to turn a simple chroot (or even a bloody box) into a binpkg producing environment, here&amp;rsquo;s a little howto &amp;hellip;&lt;/p&gt;
&lt;p&gt;First, lets start from a freshly unpacked stage3.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt" id="hl-0-1"&gt;&lt;a class="lnlinks" href="#hl-0-1"&gt;1&lt;/a&gt;
&lt;/span&gt;&lt;span class="lnt" id="hl-0-2"&gt;&lt;a class="lnlinks" href="#hl-0-2"&gt;2&lt;/a&gt;
&lt;/span&gt;&lt;span class="lnt" id="hl-0-3"&gt;&lt;a class="lnlinks" href="#hl-0-3"&gt;3&lt;/a&gt;
&lt;/span&gt;&lt;span class="lnt" id="hl-0-4"&gt;&lt;a class="lnlinks" href="#hl-0-4"&gt;4&lt;/a&gt;
&lt;/span&gt;&lt;span class="lnt" id="hl-0-5"&gt;&lt;a class="lnlinks" href="#hl-0-5"&gt;5&lt;/a&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;catalyst/x86 stage3-amd64-hardened # chroot . /bin/bash --login
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;# Now, make sure you turn on FEATURES=buildpkg
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;# (and setup anything else you need, like CFLAGS,
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;# LDFLAGS, whatever)
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;linux # echo &amp;#39;FEATURES=&amp;#34;buildpkg&amp;#34;&amp;#39; &amp;gt;&amp;gt; /etc/make.conf
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;With that single change you&amp;rsquo;re basically nearly finished with setting up the whole thing, the remaining things are just&lt;/p&gt;</description></item><item><title>Advanced bashrc ('Turning a simple chroot into a binpkg repository' continued)</title><link>https://christian.blog.pakiheim.de/posts/2014-08-08_advanced-bashrc-turning-a-simple-chroot-into-a-binpkg-repository-continued/</link><pubDate>Fri, 08 Aug 2014 09:11:14 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/2007/12/31/buildpkg-chroots/</guid><description>&lt;p&gt;As I pointed out back in &lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-08_advanced-bashrc-turning-a-simple-chroot-into-a-binpkg-repository-continued"&gt;October&lt;/a&gt;, it&amp;rsquo;s rather easy to create a setup which syncs a built binary package to a remote node (which is serving them to the world - via http,rsync,ftp - pick your poison).&lt;/p&gt;
&lt;p&gt;Now, ever since we had slight space problems on miranda ( &amp;#x1f915; my binpkgs &amp;#x1f915;), I wanted to look into methods on how to get rid of storing them on the buildnode and the webnode. I think now (hehe, it&amp;rsquo;s only 7pm), I finally managed to get a &amp;quot; &lt;em&gt;proper&lt;/em&gt;&amp;quot; bashrc which does a lot of that foo. Take a look at this:&lt;/p&gt;</description></item><item><title>packages-barfoo-org is going away</title><link>https://christian.blog.pakiheim.de/posts/2014-08-08_packages-barfoo-org-is-going-away/</link><pubDate>Fri, 08 Aug 2014 09:09:37 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=1550</guid><description>&lt;p&gt;For those of you, still using my binary packages. It&amp;rsquo;s just a waste of disk space for me (6.8G to be exact), so I decided to remove them. I&amp;rsquo;m gonna give people one week to grab yourself a copy. I&amp;rsquo;m gonna keep the bashrc and all the other stuff I wrote back when I was &lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-16_turning-a-simple-chroot-into-a-binpkg-repository" title="Advanced bashrc ('Turning a simple chroot into a binpkg repository' continued)"&gt;still interested&lt;/a&gt; in binary packages, but the binary packages &lt;strong&gt;are gonna vanish&lt;/strong&gt;!&lt;/p&gt;</description></item><item><title>Gentoo packages are gone now!</title><link>https://christian.blog.pakiheim.de/posts/2009-01-25_gentoo-packages-are-gone-now/</link><pubDate>Sun, 25 Jan 2009 14:08:30 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=1626</guid><description>&lt;p&gt;Just like &lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-08_packages-barfoo-org-is-going-away" title="packages.barfoo.org is going away"&gt;I announced last week&lt;/a&gt;, my binary packages repository is now history. I&amp;rsquo;m gonna remove the redirections from lighttpd and DNS in a few.&lt;/p&gt;</description></item></channel></rss>