How to set up a binary package server - Revision history

Fearedbliss: /* Setting up the host machine */

2013-05-30T05:45:10Z

‎Setting up the host machine

Fearedbliss: /* Setting up the host machine */

2013-05-30T05:44:18Z

‎Setting up the host machine

Fearedbliss: added directory listing

2013-05-30T05:44:04Z

added directory listing

Fearedbliss: /* Setting up the client machine */

2013-05-30T05:42:16Z

‎Setting up the client machine

Fearedbliss: /* Setting up the host machine */

2013-05-30T05:20:59Z

‎Setting up the host machine

Fearedbliss: /* Setting up the host machine */

2013-05-30T05:20:37Z

‎Setting up the host machine

Drobbins: /* Setting up the client machine */

2013-01-13T22:35:55Z

‎Setting up the client machine

Drobbins: /* Setting up the host machine */

2013-01-13T22:32:34Z

‎Setting up the host machine

Drobbins: /* What will you need? */

2013-01-13T22:31:07Z

‎What will you need?

Drobbins: /* Configuring the make.conf for host machine */

2013-01-13T22:30:40Z

‎Configuring the make.conf for host machine

@@ Line 55: / Line 55: @@
 Now that that's set, the link to your packages will be <tt>http://ip-of-computer/funtoo/packages</tt>.
-If you go to the above url now, you will get a 404 error because lighttpd by default doesn't show the directory listing. Add the following line to your /etc/lighttpd/lighttpd.conf so that if you request a page that doesn't contain an index page, it will just show the directory contents:
+If the lighttpd server were on now and you navigated to the above address, you would get a 404 error because lighttpd by default doesn't show the directory listing. Add the following line to your /etc/lighttpd/lighttpd.conf so that if you request a page that doesn't contain an index page, it will just show the directory contents:
 <console>

@@ Line 58: / Line 58: @@
 <console>
-# Activate directory listings globallydir-listing.activate = "enable"
+# Activate directory listings globally
 </console>

← Older revision		Revision as of 05:44, 30 May 2013
Line 54:		Line 54:

	Now that that's set, the link to your packages will be <tt>http://ip-of-computer/funtoo/packages</tt>.		Now that that's set, the link to your packages will be <tt>http://ip-of-computer/funtoo/packages</tt>.
		+
		+	If you go to the above url now, you will get a 404 error because lighttpd by default doesn't show the directory listing. Add the following line to your /etc/lighttpd/lighttpd.conf so that if you request a page that doesn't contain an index page, it will just show the directory contents:
		+
		+	<console>
		+	# Activate directory listings globallydir-listing.activate = "enable"
		+	</console>

	Add the service to your start up process and start it up:		Add the service to your start up process and start it up:

← Older revision		Revision as of 05:42, 30 May 2013
Line 69:		Line 69:

	To do this we need to add the <tt>--binpkg-respect-use=n</tt> to the end of emerge.		To do this we need to add the <tt>--binpkg-respect-use=n</tt> to the end of emerge.
−

	Before we use the above option, we also need to tell emerge to not only search for ebuilds, but also to search for packages as well. In order for it to search for packages, emerge will need to know where to look (the host) and set an option on portage to actually let it know to look for binaries.		Before we use the above option, we also need to tell emerge to not only search for ebuilds, but also to search for packages as well. In order for it to search for packages, emerge will need to know where to look (the host) and set an option on portage to actually let it know to look for binaries.

@@ Line 48: / Line 48: @@
 # ##i##cd /var/www/localhost/htdocs
 # ##i##mkdir funtoo && cd funtoo
 # ##i##ln -s /usr/portage portage
 # ##i##ln -s /usr/portage/distfiles distfiles
 </console>

@@ Line 64: / Line 64: @@
 === Setting up the client machine ===
-Basically the client machine will be receiving packages from a server that might not necessarily have the exact same USE flags
+Basically the client machine will be receiving packages from a server that might not necessarily have the exact same USE flags that the client machine has. Even thought we set all the USE flags on all machines to the Lowest Common Denominator, sometimes things deviate. In order to solve this problem, we will make portage not respect USE flags. Meaning that if there are different USE flags on machines, it will still install those packages.
 that the client machine has. Even thought we set all the USE flags on all machines to the Lowest Common Denominator, sometimes
 things deviate. In order to solve this problem, we will make portage not respect USE flags. Meaning that if there are different
 USE flags on machines, it will still install those packages.
-To do this we need to add the --binpkg-respect-use=n to the end of emerge.
+To do this we need to add the <tt>--binpkg-respect-use=n</tt> to the end of emerge.
-We do this by adding the --getbinpkg option to the end of emerge, and setting the PACKAGE_BINHOST variable in /etc/make.conf
+Before we use the above option, we also need to tell emerge to not only search for ebuilds, but also to search for packages as well. In order for it to search for packages, emerge will need to know where to look (the host) and set an option on portage to actually let it know to look for binaries.
-This is how my client's /etc/make.conf looks like.
+We do this by adding the <tt>--getbinpkg</tt> option to the end of emerge, and setting the <tt>PACKAGE_BINHOST</tt> variable in <tt>/etc/make.conf</tt>.
 <pre>
-    # These settings were set by the catalyst build script that automatically
+CFLAGS="-mtune=generic -O2 -pipe"
-    # built this stage.
+CXXFLAGS="${CFLAGS}"
-    # Please consult /usr/share/portage/config/make.conf.example for a more
+USE="mmx sse sse2"
-    # detailed example.
+MAKEOPTS="-j5"
 FEATURES="buildpkg userfetch getbinpkg"
-    ACCEPT_KEYWORDS="~amd64"
+EMERGE_DEFAULT_OPTS="--quiet-build=y --binpkg-respect-use=n"
-    CFLAGS="-mtune=generic -O2 -pipe"
+VIDEO_CARDS="nvidia intel"
-    CXXFLAGS="${CFLAGS}"
+INPUT_DEVICES="evdev synaptics"
-    CHOST="x86_64-pc-linux-gnu"
+LINGUAS="en en_US"
+PORTAGE_BINHOST="http://ip-address-of-build-server/gentoo/packages"
-    USE="mmx sse sse2"
-−
-    MAKEOPTS="-j5"
-−
-    FEATURES="buildpkg userfetch getbinpkg"
-−
-    EMERGE_DEFAULT_OPTS="--quiet-build=y --binpkg-respect-use=n"
-−
-    VIDEO_CARDS="nvidia intel"
-−
-    INPUT_DEVICES="evdev synaptics"
-−
-    LINGUAS="en en_US"
-−
-    PORTAGE_BINHOST="http colon //ip-address-of-build-server/gentoo/packages"
 </pre>
-After you set the package host (PORTAGE_BINHOST), set the "getbinpkg" option in FEATURES, and add "--binpkg-respect-use=n" to
+After you set the package host (via <tt>PORTAGE_BINHOST</tt>), set the <tt>getbinpkg</tt> option in <tt>FEATURES</tt>, and add <tt>--binpkg-respect-use=n</tt> to <tt>EMERGE_DEFAULT_OPTS</tt>, you are then set. Just do a emerge <tt>--sync</tt>, and <tt>emerge -uDav world</tt> or whatever you want. You should now see all your
-EMERGE_DEFAULT_OPTS, you are then set. Just do a emerge --sync, and emerge -uDav world or w/e you want. You should now see all your
 packages being pulled from the host server.
 Normally you could just do a
-<pre>
+<console>
-    # emerge -av <package> --binpkg-respect-use=n
+# ##i##emerge -av <package> --binpkg-respect-use=n
-</pre>
+</console>
-But you will have to do that each time you want to install a binary with different use flags, so in order to automate this,
+But you will have to do that each time you want to install a binary with different use flags, so in order to automate this, we add it to the <tt>EMERGE_DEFAULT_OPTS</tt>.
 we add it to the EMERGE_DEFAULT_OPTS.
 [[Category:HOWTO]]

@@ Line 39: / Line 39: @@
 Install lighttpd
-<pre>
+<console>
-    # emerge -av lighttpd
+# ##i##emerge -av lighttpd
-</pre>
+</console>
-After you install lighttpd, we will set a symlink in the htdocs folder to point to your packages folder (By default it's /usr/portage/packages)
+After you install lighttpd, we will set a symlink in the htdocs folder to point to your packages folder (By default it's <tt>/usr/portage/packages</tt>):
-<pre>
+<console>
-    # cd /var/www/localhost/htdocs
+# ##i##cd /var/www/localhost/htdocs
-    # mkdir funtoo && cd funtoo
+# ##i##mkdir funtoo && cd funtoo
-    # ln -s /usr/portage/packages packages
+# ##i##ln -s /usr/portage/packages packages
-</pre>
+</console>
-Now that that's set, the link to your packages will be http colon //ip-of-computer/funtoo/packages
+Now that that's set, the link to your packages will be <tt>http://ip-of-computer/funtoo/packages</tt>.
-Add the service to your start up process and start it up
+Add the service to your start up process and start it up:
-<pre>
+<console>
-    # rc-config add lighttpd default
+# ##i##rc-config add lighttpd default
-    # rc
+# ##i##rc
-</pre>
+</console>
 Your host machine is now ready to serve out binaries.

@@ Line 33: / Line 33: @@
 === What will you need? ===
-Besides the above advice, you will need one of the protocols that can be used for sharing (Like ftp, http, or ssh).
+Besides the above advice, you will need one of the protocols that can be used for sharing (Like FTP, HTTP, or ssh).I recommend HTTP, so we will be using lighttpd server since it's small, quick, and efficient for these basic tasks.
-−
-I recommend http, so we will be using lighttpd server since it's small, quick, and efficient for these basic tasks.
 === Setting up the host machine ===

@@ Line 29: / Line 29: @@
 </pre>
-Now that <tt>FEATURES="buildpkg"</tt> is set, from now on, every time you build a new package, it will automatically package it and you can find the <tt>.tbz2</tt> file in <tt>/usr/portage/packages</tt>.
+Now that <tt>FEATURES="buildpkg"</tt> is set, from now on, every time you build a new package, it will automatically package it and you can find the <tt>.tbz2</tt> file in <tt>/usr/portage/packages</tt> by default. You can change the destination by using the <tt>PKGDIR</tt> setting in <tt>make.conf</tt>.
 === What will you need? ===