Portage (Funtoo) - Revision history

Das-g: /* Ebuild Functions */ removed spurious space before period

2011-12-29T00:37:41Z

‎Ebuild Functions: removed spurious space before period

2011-09-23T22:56:13Z

‎In Funtoo stable/current Portage

2011-09-23T22:55:56Z

‎In Funtoo stable/current Portage

2011-09-22T01:45:27Z

‎In git

2011-01-29T04:35:01Z

2011-01-19T17:29:24Z

‎Introduction

2011-01-19T17:28:55Z

2011-01-18T01:19:28Z

2011-01-09T01:51:29Z

2011-01-09T01:48:58Z

‎In Funtoo stable/unstable Portage

@@ Line 30: / Line 30: @@
 == Ebuild Functions ==
-An ebuild developer has the ability to define [[Ebuild Functions]] that define steps to perform during a particular part of the ebuild lifecycle. These steps are now documented on their own page: [[ Ebuild Functions ]].
+An ebuild developer has the ability to define [[Ebuild Functions]] that define steps to perform during a particular part of the ebuild lifecycle. These steps are now documented on their own page: [[Ebuild Functions]].
 == Funtoo Portage Development ==

@@ Line 92: / Line 92: @@
 :There are several ebuilds in the Gentoo Portage repository that use .xz files but do not explicitly depend on xz-utils. A workaround has been added to ebuild.sh to add this dependency to metadata automatically if a .xz file exists in SRC_URI. This change is not yet in the official Portage sources but is being used on the Funtoo side when generating our git-based Portage trees.
 [[Category:Projects]]
 [[Category:Portage]]

@@ Line 75: / Line 75: @@
 ;mini-manifest
-:Funtoo's Portage supports a special mode of operation where Manifests only contain digests for distfiles and not for files in the Portage tree. This is to eliminate redundant digests since git already provides SHA1 digests. This feature is currently enabled by adding "mini-manifest" to FEATURES in /etc/make.conf but the intention is to eventually move it to a repo-specific option. Funtoo provides a special "mini-manifest" tree that is smaller than the full-size Portage tree, and is intended to be used with the mini-manifest feature.
+:Funtoo's Portage supports a special mode of operation where Manifests only contain digests for distfiles and not for files in the Portage tree. This is to eliminate redundant digests since git already provides SHA1 digests. This feature is currently enabled by adding "mini-manifest" to FEATURES in /etc/make.conf but the intention is to eventually move it to a repo-specific option (note: this has now been done, as "thin-manifest" functionality has been integrated into recent versions of Portage, and is being beta tested in Funtoo.) Funtoo provides a special "mini-manifest" tree that is smaller than the full-size Portage tree, and is intended to be used with the mini-manifest feature.
 ;preserve bindist through USE filtering

@@ Line 44: / Line 44: @@
 == Funtoo Features/Changes ==
-=== In git ===
+=== Summary ===
-;removal of emerge-webrsync, rsync code, and all related rsync variables and features
+In [https://github.com/funtoo/portage-funtoo/tree/thin-manifest the thin-manifest branch], Funtoo changes have been isolated into the following commits:
-:Not needed with git-based trees
-;initial tree clone from SYNC variable
+<pre>
-:Our Portage now finally supports the ability to initially clone a Portage tree using the git repository defined in the SYNC variable
+e5a6649e094eb7230aa8f56d97fe303f77b158e9 preserve bindist through use expansion
 === In Funtoo stable/current Portage ===

@@ Line 52: / Line 52: @@
 :Our Portage now finally supports the ability to initially clone a Portage tree using the git repository defined in the SYNC variable
-=== In Funtoo stable/unstable Portage ===
+=== In Funtoo stable/current Portage ===
 ;emerge --sync from git

@@ Line 1: / Line 1: @@
 == Introduction ==
-Portage is the official package manager of Funtoo Linux. Daniel Robbins maintains a slightly different version from upstream Gentoo Linux, with support for mini-manifests.
+Portage is the official package manager of Funtoo Linux. Daniel Robbins maintains a slightly different version from upstream Gentoo Linux, with support for mini-manifests and other features.
 == Portage Commands ==

← Older revision		Revision as of 17:28, 19 January 2011
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
−
−	~~{{Project\|hosting=http://github.com/funtoo/portage-funtoo}}~~

	Portage is the official package manager of Funtoo Linux. Daniel Robbins maintains a slightly different version from upstream Gentoo Linux, with support for mini-manifests.		Portage is the official package manager of Funtoo Linux. Daniel Robbins maintains a slightly different version from upstream Gentoo Linux, with support for mini-manifests.

@@ Line 40: / Line 40: @@
 === TODO ===
-Add support to portage, so that when an ebuild is merged, the /var/db/pkg entry contains a list of all currently-installed versions of all ebuilds upon which that ebuild RDEPENDs. This, combined with a comprehensive set of past USE settings (may need to implement this too,) can be used to detect when an ebuild needs to be rebuilt. This could help to address issues like those in [http://bugs.gentoo.org/167662 Gentoo Bug 167662] and allow easier implementation of support for things like perl-cleaner.
+Add support to portage, so that when an ebuild is merged, the /var/db/pkg entry contains a list of all currently-installed versions of all ebuilds upon which that ebuild RDEPENDs. This, combined with a comprehensive set of past USE settings (may need to implement this too,) can be used to detect when an ebuild needs to be rebuilt. This could help to address issues like those in [http://bugs.gentoo.org/167662 Gentoo Bug 167662] and allow easier implementation of support for things like perl-cleaner. Currently, perl-cleaner doesn't detect that vim uses perl and moving from -ithreads to ithreads causes vim to die, so it needs to be manually rebuilt.
 Add support for portage to understand which version of a particular app is the "active" version that it was built against, and record this information in /var/db/pkg. This can help to implement perl-cleaner-like support in Portage.

@@ Line 57: / Line 57: @@
 ;emerge --sync from git
-:If a git-based Portage tree is already in place, <tt>emerge --sync</tt> will run "git pull" to update the underlying Portage tree.
+:If a git-based Portage tree is already in place, <tt>emerge --sync</tt> will run "git pull" to update the underlying Portage tree. If one is not in place, the contents of the SYNC variable will be used as the remote URI from which to clone a git tree (2.2). In addition, SYNC_USER and SYNC_UMASK (defaulting to root and 022) can be used to define the user account to use for cloning/syncing, as well as the umask to use. (2.2).
 ;Sed Wrapper Symlink and PATH fix