<?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: Privatization means rebuilds	</title>
	<atom:link href="https://www.dragonflydigest.com/2016/01/27/privatization-means-rebuilds/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2016/01/27/privatization-means-rebuilds/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Sat, 30 Jan 2016 15:03:01 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: s4		</title>
		<link>https://www.dragonflydigest.com/2016/01/27/privatization-means-rebuilds/comment-page-1/#comment-357533</link>

		<dc:creator><![CDATA[s4]]></dc:creator>
		<pubDate>Sat, 30 Jan 2016 15:03:01 +0000</pubDate>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=17547#comment-357533</guid>

					<description><![CDATA[Thanks for explanation, Justin! Everything became clearer.]]></description>
			<content:encoded><![CDATA[<p>Thanks for explanation, Justin! Everything became clearer.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: More on privatization &#8211; DragonFly BSD Digest		</title>
		<link>https://www.dragonflydigest.com/2016/01/27/privatization-means-rebuilds/comment-page-1/#comment-357492</link>

		<dc:creator><![CDATA[More on privatization &#8211; DragonFly BSD Digest]]></dc:creator>
		<pubDate>Sat, 30 Jan 2016 03:03:36 +0000</pubDate>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=17547#comment-357492</guid>

					<description><![CDATA[[&#8230;] those of you running DragonFly-current, the already-mentioned library privatization going on means that ports have to be rebuilt.  You will want to do it yourself, or wait a little [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] those of you running DragonFly-current, the already-mentioned library privatization going on means that ports have to be rebuilt.  You will want to do it yourself, or wait a little [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Justin Sherrill		</title>
		<link>https://www.dragonflydigest.com/2016/01/27/privatization-means-rebuilds/comment-page-1/#comment-357483</link>

		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Fri, 29 Jan 2016 21:16:31 +0000</pubDate>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=17547#comment-357483</guid>

					<description><![CDATA[I may have confused the issue a bit by mentioning perl - this isn&#039;t a system language issue, rather system libraries.  DragonFly comes with libcurses (for example; there are other libraries) installed for a variety of things , but there&#039;s a different and sometimes newer version of curses in ports.

There are programs in ports that need curses, and so have dependencies on libcurses when being built.  Those ports have curses as a dependency, and so will bring it in automatically when building.  However, it&#039;s possible that the version of libcurses already in the system will get linked instead of the ports version, so the ports software getting built could end up with the wrong library versions installed.

This walls off the system versions of various libraries, so that what gets built and linked with ports is the known, correct versions from ports.  The same goes for system stuff - it will never get accidentally linked with a ports version of something and then break when that port is upgraded.]]></description>
			<content:encoded><![CDATA[<p>I may have confused the issue a bit by mentioning perl &#8211; this isn&#8217;t a system language issue, rather system libraries.  DragonFly comes with libcurses (for example; there are other libraries) installed for a variety of things , but there&#8217;s a different and sometimes newer version of curses in ports.</p>
<p>There are programs in ports that need curses, and so have dependencies on libcurses when being built.  Those ports have curses as a dependency, and so will bring it in automatically when building.  However, it&#8217;s possible that the version of libcurses already in the system will get linked instead of the ports version, so the ports software getting built could end up with the wrong library versions installed.</p>
<p>This walls off the system versions of various libraries, so that what gets built and linked with ports is the known, correct versions from ports.  The same goes for system stuff &#8211; it will never get accidentally linked with a ports version of something and then break when that port is upgraded.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: s4		</title>
		<link>https://www.dragonflydigest.com/2016/01/27/privatization-means-rebuilds/comment-page-1/#comment-357482</link>

		<dc:creator><![CDATA[s4]]></dc:creator>
		<pubDate>Fri, 29 Jan 2016 21:01:26 +0000</pubDate>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=17547#comment-357482</guid>

					<description><![CDATA[For example, lets take CentOS 6, which uses python 2.6 as system language (suppose v2.6.2). So when I&#039;ll install python-2.6.6.rpm I&#039;ll update a system library and this may break the system. With &quot;privatization&quot; I can have v2.6.2 and v2.6.6 at the same time. Am I right? I just can&#039;t understand what &quot;privatization&quot; is.]]></description>
			<content:encoded><![CDATA[<p>For example, lets take CentOS 6, which uses python 2.6 as system language (suppose v2.6.2). So when I&#8217;ll install python-2.6.6.rpm I&#8217;ll update a system library and this may break the system. With &#8220;privatization&#8221; I can have v2.6.2 and v2.6.6 at the same time. Am I right? I just can&#8217;t understand what &#8220;privatization&#8221; is.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
