Portage Dynamic Slot - Revision history

Drobbins at 03:29, 12 November 2011

2011-11-12T03:29:26Z

Drobbins: /* Dynamic SLOT */

2011-09-27T15:18:37Z

‎Dynamic SLOT

Drobbins: /* Dynamic SLOT */

2011-09-27T01:06:37Z

‎Dynamic SLOT

Drobbins: /* Traditional SLOT */

2011-09-27T01:04:57Z

‎Traditional SLOT

Drobbins: /* Requirements */

2011-09-27T01:02:08Z

‎Requirements

Drobbins at 00:59, 27 September 2011

2011-09-27T00:59:29Z

Drobbins: /* Requirements */

2011-09-27T00:57:02Z

‎Requirements

Drobbins at 00:55, 27 September 2011

2011-09-27T00:55:59Z

Drobbins: /* Traditional SLOT */

2011-09-27T00:53:23Z

‎Traditional SLOT

Drobbins: /* Dynamic SLOT */

2011-09-27T00:52:16Z

‎Dynamic SLOT

← Older revision		Revision as of 03:29, 12 November 2011
Line 62:		Line 62:
	[[Category:Portage]]		[[Category:Portage]]
	[[Category:Labs]]		[[Category:Labs]]
−	~~[[Category:Featured]]~~

@@ Line 22: / Line 22: @@
      if use custom && has "${EBUILD_PHASE:none}" "unpack" "prepare" "compile" "install"; then
          if [ -n "$CUSTOM_CONFIG" ]; then
-             SLOT="$PV-$(dirname $CUSTOM_CONFIG)"
+             SLOT="$PV-${CUSTOM_CONFIG##*/}"
          else
              die "Please define CUSTOM_CONFIG to use 'custom' USE variable"

@@ Line 20: / Line 20: @@
 pkg_setup() {
-     if has "${EBUILD_PHASE:none}" "unpack" "prepare" "compile" "install"; then
+     if use custom && has "${EBUILD_PHASE:none}" "unpack" "prepare" "compile" "install"; then
          if [ -n "$CUSTOM_CONFIG" ]; then
              SLOT="$PV-$(dirname $CUSTOM_CONFIG)"

@@ Line 5: / Line 5: @@
 == Traditional SLOT ==
-Historically, Portage has supported SLOTs, which are defined statically in the ebuild and allow certain package versions to be installed alongside other versions of the same package. For example, <tt>libpng-1.4.2</tt> could have a <tt>SLOT</tt> of <tt>"1.4"</tt> while libpng-1.5 could have a <tt>SLOT</tt> of <tt>"1.5"</tt>. This indicates that these ebuilds can be installed alongside each other.
+Historically, Portage has supported SLOTs, which are defined statically in the ebuild and allow certain package versions to be installed alongside other versions of the same package. For example, <tt>libpng-1.4.2</tt> could have a <tt>SLOT</tt> of <tt>"1.4"</tt> while <tt>libpng-1.5</tt> could have a <tt>SLOT</tt> of <tt>"1.5"</tt>. This indicates that these ebuilds can be installed alongside each other.
 It has been the policy of Gentoo Linux to only allow <tt>SLOT</tt> to be set statically in the ebuild, and not vary (via code) within the ebuild. Traditionally, within a single ebuild it must always be the same, non-variable value.

@@ Line 51: / Line 51: @@
 * <tt>pkg_setup</tt> should override the SLOT only in certain required phases that reference the dynamic SLOT. Use <tt>EBUILD_PHASE</tt> for this, as in the example.
 * Ensure that files in your ebuild are installed to different locations so that they do not conflict with any other installed versions of this ebuild.
 == Implementation ==

@@ Line 47: / Line 47: @@
 == Requirements ==
-* A default <tt>SLOT</tt> value must be defined in the main body of the ebuild, as normal. This value is cached in the metadata.
+* A default <tt>SLOT</tt> value must be defined in the main body of the ebuild, as normal, and just like a traditional <tt>SLOT</tt>, it must not vary within an individual ebuild. This value is cached in the metadata.
 * <tt>pkg_setup</tt> can be used to override <tt>SLOT</tt> but this should not be the default behavior. It should be enabled via USE variable.
 * <tt>pkg_setup</tt> should override the SLOT only in certain required phases that reference the dynamic SLOT. Use <tt>EBUILD_PHASE</tt> for this, as in the example.
-* Ensure that files are installed to different locations to ensure they do not conflict with any other SLOTs for this ebuild.
+* Ensure that files in your ebuild are installed to different locations so that they do not conflict with any other installed versions of this ebuild.
 [[Category:Portage]]
 [[Category:Labs]]
 [[Category:Featured]]

@@ Line 5: / Line 5: @@
 Historically, Portage has supported SLOTs, which are defined statically in the ebuild and allow certain package versions to be installed alongside other versions of the same package. For example, libpng-1.4.2 could have a SLOT of "1.4" while libpng-1.5 could have a SLOT of "1.5". This indicates that these ebuilds can be installed alongside each other.
-It has been the policy of Gentoo Linux to only allow SLOT to be set statically in the ebuild, and not vary (via code) within the ebuild.
+It has been the policy of Gentoo Linux to only allow <tt>SLOT</tt> to be set statically in the ebuild, and not vary (via code) within the ebuild. Traditionally, within a single ebuild it must always be the same, non-variable value.
 == Dynamic SLOT ==

@@ Line 9: / Line 9: @@
 == Dynamic SLOT ==
-Funtoo dynamic slot functionality changes this policy and allows SLOT to vary. This is useful for custom builds of an application whose paths are defined by an external variable passed in to Portage.
+Funtoo dynamic slot functionality changes this policy and allows <tt>SLOT</tt> to vary. This is useful for custom builds of an application whose paths are defined by an external variable passed in to Portage.
 Here is an example of how dynamic slot works in an ebuild, and shows how it is intended to be used -- to allow custom versions of ebuilds to be built alongside non-custom versions:
@@ Line 39: / Line 39: @@
 </pre>
-Above, the same ebuild has a USE flag called "custom". When it is set, the ebuild looks for a variable called CUSTOM_CONFIG in the environment (this would typically be exported into the current shell.) The name of the CUSTOM_CONFIG file is used to modify SLOT, so that if CUSTOM_CONFIG pointed to /foo/bar/oni, and the ebuild version was 1.0-r1, then SLOT would be set to 1.0-oni.
+Above, the ebuild has a USE flag called "custom". When it is set, the ebuild looks for a variable called <tt>CUSTOM_CONFIG</tt> in the environment (this would typically be exported into the current shell.) The name of the <tt>CUSTOM_CONFIG</tt> file is used to modify <tt>SLOT</tt>, so that if <tt>CUSTOM_CONFIG</tt> pointed to <tt>/foo/bar/oni</tt>, and the ebuild version was <tt>1.0-r1</tt>, then <tt>SLOT</tt> would be set to <tt>1.0-oni</tt>.
 Also note that this ebuild takes care to ensure that the ebuild modifies all paths so that the files in this ebuild will not conflict with the paths in other versions of this ebuild. This is how dynamic slot is intended to be used. I plan to use this functionality in Funtoo Linux to support custom kernel ebuilds.