<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Putting Oracle Database in a deb package for ubuntu</title>
	<atom:link href="http://blog.loftninjas.org/2007/10/12/putting-oracle-database-in-a-deb-package-for-ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.loftninjas.org/2007/10/12/putting-oracle-database-in-a-deb-package-for-ubuntu/</link>
	<description></description>
	<lastBuildDate>Sat, 21 Jan 2012 06:46:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: btm</title>
		<link>http://blog.loftninjas.org/2007/10/12/putting-oracle-database-in-a-deb-package-for-ubuntu/comment-page-1/#comment-133</link>
		<dc:creator>btm</dc:creator>
		<pubDate>Wed, 24 Oct 2007 20:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.loftninjas.org/?p=83#comment-133</guid>
		<description>No. &lt;br/&gt;&lt;br/&gt;Actually the python build script installs oracle on the local machine in headless mode mostly automatically. Then it copies (tars) it all to a deb build directory and runs dpkg-deb or such (I forget) to build a deb from the binaries.&lt;br/&gt;&lt;br/&gt;The oracle installer even in headless mode is pretty difficult to work around in an automated way. The first problem being that when you start it, it forks. This didn&#039;t sound fun to mess with.&lt;br/&gt;&lt;br/&gt;In the end, it was needed in a deb for version tracking, upgrades, testing, etc.</description>
		<content:encoded><![CDATA[<p>No. </p>
<p>Actually the python build script installs oracle on the local machine in headless mode mostly automatically. Then it copies (tars) it all to a deb build directory and runs dpkg-deb or such (I forget) to build a deb from the binaries.</p>
<p>The oracle installer even in headless mode is pretty difficult to work around in an automated way. The first problem being that when you start it, it forks. This didn&#8217;t sound fun to mess with.</p>
<p>In the end, it was needed in a deb for version tracking, upgrades, testing, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: benjamin</title>
		<link>http://blog.loftninjas.org/2007/10/12/putting-oracle-database-in-a-deb-package-for-ubuntu/comment-page-1/#comment-132</link>
		<dc:creator>benjamin</dc:creator>
		<pubDate>Wed, 24 Oct 2007 19:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.loftninjas.org/?p=83#comment-132</guid>
		<description>So your deb simply runs the oracle installer in headless mode? uhm why do u need the deb then? easier to uninstall upgrade etc. is that it? Why not just have the deb copy the binarys etc from an existing i386 install sumwhere and have any conf file changes needed be done via scripts in the debian directory?</description>
		<content:encoded><![CDATA[<p>So your deb simply runs the oracle installer in headless mode? uhm why do u need the deb then? easier to uninstall upgrade etc. is that it? Why not just have the deb copy the binarys etc from an existing i386 install sumwhere and have any conf file changes needed be done via scripts in the debian directory?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

