Maemo-releases - Revision history

amigadave: mark as {{out of date}}

2010-06-18T11:40:52Z

mark as {{out of date}}

← Older revision		Revision as of 11:40, 18 June 2010
Line 1:		Line 1:
		+	{{out of date}}
		+
	== The rationale behind maemo-release ==		== The rationale behind maemo-release ==

Line 5:		Line 7:
	Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.		Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.

-	This results in having to provide a different debian/control file for the various distributions, which in turn forces one to make a different debian/changelog file for the various distributions. At this point, different distributions have different source packages.	+	This results in having to provide a different <code>debian/control</code> file for the various distributions, which in turn forces one to make a different <code>debian/changelog</code> file for the various distributions. At this point, different distributions have different source packages.

-	To prevent this one reason for forking the source package, we need the maemo-release package. Then, knowing which distribution(s) contain a needed package foo, we can create an appropriate debian/control entry.	+	To prevent this one reason for forking the source package, we need the maemo-release package. Then, knowing which distribution(s) contain a needed package foo, we can create an appropriate <code>debian/control</code> entry.

	Example: Suppose Bora and Diablo contain package foo, but the other distributions do not. The corresponding debian/control Build-Depends entry will be:		Example: Suppose Bora and Diablo contain package foo, but the other distributions do not. The corresponding debian/control Build-Depends entry will be:

-	<~~code~~>	+	<pre>
-	Build-Depends: package1-dev,	+	Build-Depends: package1-dev,
-	package2-dev,	+	package2-dev,
-	...,	+	...,
-	foo \| maemo-release (= 1.0.0) \| maemo-release (= 3.0.0) \| maemo-release (= 5.0.0),	+	foo \| maemo-release (= 1.0.0) \| maemo-release (= 3.0.0) \| maemo-release (= 5.0.0),
-	...,	+	...,
-	packagen-dev	+	packagen-dev
-	</~~code~~>	+	</pre>

	This way you can describe intervals of distributions wherein a certain package has become available. Examples:		This way you can describe intervals of distributions wherein a certain package has become available. Examples:

amigadave: add link

2010-05-06T12:43:43Z

add link

← Older revision		Revision as of 12:43, 6 May 2010
Line 1:		Line 1:
	== The rationale behind maemo-release ==		== The rationale behind maemo-release ==

-	The maemo-release package seeks to address the situation wherein a source package is forked into gregale/bora/chinook/[[Open development/Maemo roadmap/Diablo\|diablo]]/[[Open development/Maemo roadmap/Fremantle\|fremantle]] versions of itself because one set of Build-Depends does not work for all distributions.	+	The [http://maemo.org/packages/view/maemo-release/ maemo-release package] seeks to address the situation wherein a source package is forked into gregale/bora/chinook/[[Open development/Maemo roadmap/Diablo\|diablo]]/[[Open development/Maemo roadmap/Fremantle\|fremantle]] versions of itself because one set of Build-Depends does not work for all distributions.

	Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.		Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.

amigadave: wikify

2010-02-19T10:51:36Z

wikify

← Older revision		Revision as of 10:51, 19 February 2010
Line 1:		Line 1:
	== The rationale behind maemo-release ==		== The rationale behind maemo-release ==

-	The maemo-release package seeks to address the situation wherein a source package is forked into gregale/bora/chinook/diablo/fremantle versions of itself because one set of Build-Depends does not work for all distributions.	+	The maemo-release package seeks to address the situation wherein a source package is forked into gregale/bora/chinook/[[Open development/Maemo roadmap/Diablo\|diablo]]/[[Open development/Maemo roadmap/Fremantle\|fremantle]] versions of itself because one set of Build-Depends does not work for all distributions.

	Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.		Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.
Line 54:		Line 54:

	Of course, the rest of the build process has also to be made tolerant of the presence/absence of a given package.		Of course, the rest of the build process has also to be made tolerant of the presence/absence of a given package.
		+
		+	[[Category:Development]]

192.100.124.219: /* The rationale behind maemo-release */

2009-10-29T13:32:00Z

The rationale behind maemo-release

← Older revision		Revision as of 13:32, 29 October 2009
Line 36:		Line 36:
	\|-		\|-
	\|-		\|-
-	\|colspan="5" style="border:1px solid;" \| Example: <code>foo \| maemo-release (< 2.0.0) \| maemo-release (> 4.0.0)</code>	+	\|colspan="5" style="border:1px solid;" \| Example: <code>foo \| maemo-release (< 3.0.0) \| maemo-release (> 4.0.0)</code>
	\|-		\|-
	\| align="center" style="background:red; color:white" colspan="2" \| foo is absent		\| align="center" style="background:red; color:white" colspan="2" \| foo is absent

192.100.124.219: /* The rationale behind maemo-release */

2009-10-29T13:24:12Z

The rationale behind maemo-release

← Older revision		Revision as of 13:24, 29 October 2009
Line 52:		Line 52:
	\|-		\|-
	\|}		\|}
		+
		+	Of course, the rest of the build process has also to be made tolerant of the presence/absence of a given package.

192.100.124.219: /* The rationale behind maemo-release */

2009-10-29T13:21:22Z

The rationale behind maemo-release

← Older revision		Revision as of 13:21, 29 October 2009
Line 15:		Line 15:
	package2-dev,		package2-dev,
	...,		...,
-	foo \| maemo-~~version~~ (= 1.0.0) \| maemo-~~version~~ (= 3.0.0) \| maemo-~~version~~ (= 5.0.0),	+	foo \| maemo-release (= 1.0.0) \| maemo-release (= 3.0.0) \| maemo-release (= 5.0.0),
	...,		...,
	packagen-dev		packagen-dev
Line 40:		Line 40:
	\| align="center" style="background:red; color:white" colspan="2" \| foo is absent		\| align="center" style="background:red; color:white" colspan="2" \| foo is absent
	\| align="center" style="background:green; color:white" colspan="2" \| foo is present		\| align="center" style="background:green; color:white" colspan="2" \| foo is present
		+	\| align="center" style="background:red; color:white" colspan="1" \| foo is absent
		+	\|-
		+	\|-
		+	\|colspan="5" style="border:1px solid;" \| Example: <code>foo \| maemo-release (= 1.0.0) \| maemo-release (= 3.0.0) \| maemo-release (= 5.0.0)</code>
		+	\|-
		+	\| align="center" style="background:red; color:white" colspan="1" \| foo is absent
		+	\| align="center" style="background:green; color:white" colspan="1" \| foo is present
		+	\| align="center" style="background:red; color:white" colspan="1" \| foo is absent
		+	\| align="center" style="background:green; color:white" colspan="1" \| foo is present
	\| align="center" style="background:red; color:white" colspan="1" \| foo is absent		\| align="center" style="background:red; color:white" colspan="1" \| foo is absent
	\|-		\|-
	\|}		\|}

192.100.124.219: New page

2009-10-29T13:17:27Z

New page

New page

== The rationale behind maemo-release ==

The maemo-release package seeks to address the situation wherein a source package is forked into gregale/bora/chinook/diablo/fremantle versions of itself because one set of Build-Depends does not work for all distributions.

Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.

This results in having to provide a different debian/control file for the various distributions, which in turn forces one to make a different debian/changelog file for the various distributions. At this point, different distributions have different source packages.

To prevent this one reason for forking the source package, we need the maemo-release package. Then, knowing which distribution(s) contain a needed package foo, we can create an appropriate debian/control entry.

Example: Suppose Bora and Diablo contain package foo, but the other distributions do not. The corresponding debian/control Build-Depends entry will be:

<code>
Build-Depends: package1-dev,
package2-dev,
...,
foo | maemo-version (= 1.0.0) | maemo-version (= 3.0.0) | maemo-version (= 5.0.0),
...,
packagen-dev
</code>

This way you can describe intervals of distributions wherein a certain package has become available. Examples:

{|style="border:1px solid;"
|-
!align="center"|   (1.0.0) Gregale  
!align="center"|   (2.0.0) Bora  
!align="center"|   (3.0.0) Chinook  
!align="center"|   (4.0.0) Diablo  
!align="center"|   (5.0.0) Fremantle  
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 3.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="3" | foo is present
|-
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 2.0.0) | maemo-release (> 4.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="2" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
|-
|}