Funtoo Linux FAQ - Revision history

Oleg: Reverted edits by 37.59.80.67 (talk) to last revision by Atzorvas

2012-06-24T11:33:04Z

Reverted edits by 37.59.80.67 (talk) to last revision by Atzorvas

Show changes

37.59.80.67: Anh con may cung nhau xem nha

2012-06-24T10:03:33Z

Anh con may cung nhau xem nha

Show changes

Atzorvas: /* Where can I learn more about git? -- fixing dead-link for git guide*/

2012-04-21T21:29:04Z

‎Where can I learn more about git? -- fixing dead-link for git guide

Mmatk: /* I can't use emerge --sync to download an initial Portage tree. */

2012-04-14T17:20:52Z

‎I can't use emerge --sync to download an initial Portage tree.

80.97.15.149: /* I have forked my own Portage tree. How do I generate metadata for it? */

2012-03-20T15:23:59Z

‎I have forked my own Portage tree. How do I generate metadata for it?

117.202.115.148: /* Is Paludis compatible with the Funtoo Portage tree? */

2012-02-29T05:11:43Z

‎Is Paludis compatible with the Funtoo Portage tree?

Tbrass: /* I can't use emerge --sync to download an initial Portage tree. */

2011-08-29T05:23:56Z

‎I can't use emerge --sync to download an initial Portage tree.

Rh1: Removed repo.conf alias instructions, not needed anymore

2011-07-08T01:09:40Z

Removed repo.conf alias instructions, not needed anymore

Rh1 at 04:04, 2 March 2011

2011-03-02T04:04:09Z

Tintamarre: /* How do I report a bug? */ Add a link to reporting bugs page

2011-02-25T09:47:47Z

‎How do I report a bug?: Add a link to reporting bugs page

@@ Line 279: / Line 279: @@
 === Where can I learn more about <tt>git</tt>? ===
-So, you want to learn more about <tt>git</tt>, do you? A collection of excellent git resources is now available on the [[dev-vcs/git|git ebuild page]].
+So, you want to learn more about <tt>git</tt>, do you? A collection of excellent git resources is now available on the [[Git Guide]].
 [[Category:HOWTO]]

@@ Line 28: / Line 28: @@
 Make sure you have the following in /etc/make.conf
 <pre>
-SYNC="git://github.com/funtoo/portage-mini-2011.git"
+SYNC="git://github.com/funtoo/ports-2012.git"
 </pre>

@@ Line 268: / Line 268: @@
 You should only do this if you are creating a unified Portage tree for distribution to users. Otherwise, it is much more efficient to use an overlay for this purpose.
-First, add <tt>FEATURES=&quot;metadata-transfer</tt> to your <tt>/etc/make.conf</tt> file. Then type the following commands:
+First, add <tt>FEATURES=&quot;metadata-transfer&quot;</tt> to your <tt>/etc/make.conf</tt> file. Then type the following commands:
 <pre># cd /usr/portage

@@ Line 145: / Line 145: @@
 === Is Paludis compatible with the Funtoo Portage tree? ===
-Paludis does not appear to be compatible with the Funtoo Portage tree, unfortunately. It does not support the <tt>package.mask</tt> directory without additional hooks, and also does not support merging device nodes. These features are supported by by Portage and we use both of these capabilities. I think that both <tt>package.mask</tt> (and <tt>package.keywords</tt>, etc.) directories are a good idea, and I also think it's a good idea for the package manager to support device nodes, which is particularly useful for the <tt>udev</tt> and <tt>baselayout</tt> ebuilds. Funtoo Linux has separate versions of these packages, and these ebuilds are easier to maintain if device nodes are correctly supported by the package manger, and the <tt>package.mask</tt> directory is a great help to us as well.
+Paludis does not appear to be compatible with the Funtoo Portage tree, unfortunately. It does not support the <tt>package.mask</tt> directory without additional hooks, and also does not support merging device nodes. These features are supported by Portage and we use both of these capabilities. I think that both <tt>package.mask</tt> (and <tt>package.keywords</tt>, etc.) directories are a good idea, and I also think it's a good idea for the package manager to support device nodes, which is particularly useful for the <tt>udev</tt> and <tt>baselayout</tt> ebuilds. Funtoo Linux has separate versions of these packages, and these ebuilds are easier to maintain if device nodes are correctly supported by the package manger, and the <tt>package.mask</tt> directory is a great help to us as well.
 We could maintain a patched version of Paludis that would be useable with the Funtoo Portage tree, but I don't want to get into the business of supporting a non-standard package manager as the upstream project seems not seem very supportive of getting these compatibility issues resolved, and thus this could turn into a maintenance burden for Funtoo. So I'd rather just not support Paludis for now.

@@ Line 28: / Line 28: @@
 Make sure you have the following in /etc/make.conf
 <pre>
-SYNC="git://github.com/funtoo/portage-mini-2010.git"
+SYNC="git://github.com/funtoo/portage-mini-2011.git"
 </pre>
 === I try to emerge something and Portage complains that a digest is not found. ===

@@ Line 132: / Line 132: @@
 # mv ../distfiles .</pre>
 Now everything should be working again.
 === How do I tell if a problem I am having originates from Gentoo or Funtoo? ===

@@ Line 26: / Line 26: @@
 === I can't use <tt>emerge --sync</tt> to download an initial Portage tree. ===
-Yes, Portage doesn't do that yet. To grab an initial Portage tree, download a current git-based snapshot from [http://ftp.osuosl.org/pub/funtoo/~funtoo/snapshots/ the Funtoo Portage snapshot repository]. Then, type the following commands:
+Make sure you have the following in /etc/make.conf
 <pre>
-<pre># cd /usr
+SYNC="git://github.com/funtoo/portage-mini-2010.git"
-# tar xf /path/to/portage-current.tar.xz
+</pre>
-# cd portage
-# git checkout funtoo.org</pre>
-Once you have git-based Portage tree in place, Portage 2.2 will realize that you are using Funtoo Linux and will perform git updates rather than rsync updates when you type <tt>emerge --sync</tt>.
-−
-You will need to add the following to <tt>/etc/make.conf</tt> to use Portage mini-Manifests:
-−
-<pre>FEATURES=&quot;mini-manifest&quot;</pre>
 === I try to emerge something and Portage complains that a digest is not found. ===

← Older revision		Revision as of 09:47, 25 February 2011
Line 171:		Line 171:

	If you report a bug to Gentoo that may impact Funtoo Linux in some way, please post information about it to the [http://groups.google.com/group/funtoo-dev funtoo-dev mailing list] so we are aware of the issue.		If you report a bug to Gentoo that may impact Funtoo Linux in some way, please post information about it to the [http://groups.google.com/group/funtoo-dev funtoo-dev mailing list] so we are aware of the issue.
		+
		+	* More informations: [[Reporting Bugs\|Guidelines for Reporting Bugs]].

	=== How do I become a Funtoo developer? ===		=== How do I become a Funtoo developer? ===