<?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: More sensible comments on cabal-debian</title>
	<atom:link href="http://therning.org/magnus/archives/485/feed" rel="self" type="application/rss+xml" />
	<link>http://therning.org/magnus/archives/485</link>
	<description>Incoherent mumblings</description>
	<lastBuildDate>Wed, 08 Aug 2012 00:21:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Adam Jones</title>
		<link>http://therning.org/magnus/archives/485/comment-page-1#comment-215011</link>
		<dc:creator>Adam Jones</dc:creator>
		<pubDate>Sat, 02 Apr 2011 05:10:01 +0000</pubDate>
		<guid isPermaLink="false">http://therning.org/magnus/?p=485#comment-215011</guid>
		<description><![CDATA[&lt;p&gt;Well, I&#039;ve seen that information generated from a &lt;em&gt;source build&lt;/em&gt;
(debuild -S is what I tend to use).  I suppose it could be incomplete
if the rules file modifies the control file.  I would hope that&#039;s a
fairly rare setup though.  Surely it isn&#039;t something that cabal-debian
engages in, right?&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Well, I&#8217;ve seen that information generated from a <em>source build</em>
(debuild -S is what I tend to use).  I suppose it could be incomplete
if the rules file modifies the control file.  I would hope that&#8217;s a
fairly rare setup though.  Surely it isn&#8217;t something that cabal-debian
engages in, right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Shaw</title>
		<link>http://therning.org/magnus/archives/485/comment-page-1#comment-169245</link>
		<dc:creator>Jeremy Shaw</dc:creator>
		<pubDate>Sat, 24 Jan 2009 22:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://therning.org/magnus/?p=485#comment-169245</guid>
		<description><![CDATA[&lt;p&gt;Hello,&lt;/p&gt;

&lt;p&gt;Sorry, we are using the version of haskell-devscripts that is maintained by Arjan Oosting as well -- I forgot that the maintainer for that package had changed.&lt;/p&gt;

&lt;p&gt;Here is the current state of things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;I have uploaded a newer version of the debian library to hackage (version 3.18.1). (the cabal-debian binary is part of this cabal package. The darcs repo named cabal-debian is obsolete, and is being moved into the attic).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;the patches to haskell-devscripts are now split into some quilt patches.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;we have debianized the latest version of hlibrary.mk so that it gets installed globally, (similar to gnome.mk, kde.mk, etc). We also added some patches so that it can use cabal-debian to generate binary dependencies, and do some other checks.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;http://src.seereason.com/ghc610/quilt/haskell-devscripts-quilt/
http://src.seereason.com/ghc610/haskell-cdbs/&lt;/p&gt;

&lt;p&gt;There are still some unresolved issues though -- such as cabal-debian build-depending on itself.&lt;/p&gt;

&lt;p&gt;I&#039;ll keep you posted.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Hello,</p>

<p>Sorry, we are using the version of haskell-devscripts that is maintained by Arjan Oosting as well &#8212; I forgot that the maintainer for that package had changed.</p>

<p>Here is the current state of things:</p>

<ul>
<li><p>I have uploaded a newer version of the debian library to hackage (version 3.18.1). (the cabal-debian binary is part of this cabal package. The darcs repo named cabal-debian is obsolete, and is being moved into the attic).</p></li>
<li><p>the patches to haskell-devscripts are now split into some quilt patches.</p></li>
<li><p>we have debianized the latest version of hlibrary.mk so that it gets installed globally, (similar to gnome.mk, kde.mk, etc). We also added some patches so that it can use cabal-debian to generate binary dependencies, and do some other checks.</p></li>
</ul>

<p><a href="http://src.seereason.com/ghc610/quilt/haskell-devscripts-quilt/" rel="nofollow">http://src.seereason.com/ghc610/quilt/haskell-devscripts-quilt/</a>
<a href="http://src.seereason.com/ghc610/haskell-cdbs/" rel="nofollow">http://src.seereason.com/ghc610/haskell-cdbs/</a></p>

<p>There are still some unresolved issues though &#8212; such as cabal-debian build-depending on itself.</p>

<p>I&#8217;ll keep you posted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Magnus</title>
		<link>http://therning.org/magnus/archives/485/comment-page-1#comment-169106</link>
		<dc:creator>Magnus</dc:creator>
		<pubDate>Fri, 23 Jan 2009 07:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://therning.org/magnus/?p=485#comment-169106</guid>
		<description><![CDATA[&lt;p&gt;@Jeremy,&lt;/p&gt;

&lt;p&gt;First of all, thanks for commenting on this at all :-)&lt;/p&gt;

&lt;p&gt;I think the best route is to get things into Debian.  The &lt;code&gt;haskell-devscripts&lt;/code&gt; I have on my Sid system is maintained by Arjan Oosting though, not by John Goerzen.  I don&#039;t know if I can help in any way in convincing the maintainer to include your changes, and ideally to also upload cabal-debian itself to Debian proper, but I&#039;d be more than willing to chip in if you want me to.  Arjan, if you are reading this, please help out a poor Debian user here!  ;-)&lt;/p&gt;

&lt;p&gt;I&#039;ll try to explain what I mean with the second item.  During building of the package &lt;code&gt;dh_haskell_prep&lt;/code&gt; is called and it generates two snippets, &lt;code&gt;libghc6-dataenc-dev.postinst.debhelper&lt;/code&gt; and &lt;code&gt;libghc6-dataenc-dev.prerm.debhelper&lt;/code&gt;.  The former has the following contents (taken from my use of cabal-debian on dataenc):&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# Automatically added by dh_haskell_prep
GHC_PKG=/usr/lib/ghc-6.8.2/bin/ghc-pkg 
CONFIGFILE=/usr/lib/haskell-packages/ghc6/lib/dataenc-0.12/installed-pkg-config


case &quot;$1&quot; in
    abort-deconfigure&#124;abort-remove&#124;abort-upgrade&#124;configure)
    OLDVERSIONS=`$GHC_PKG --global field dataenc version 2&gt; /dev/null &#124; sed &quot;s/version: //&quot;`
    for VERSION in $OLDVERSIONS ; do
        $GHC_PKG --global hide dataenc-$VERSION &#124;&#124; true
    done
    $GHC_PKG --global --auto-ghci-libs register $CONFIGFILE
    ;;
    *)
        echo &quot;postinst called with unknown argument \`$1&#039;&quot; &gt;&amp;2
        exit 1
    ;;
esac



# arch-tag: haskell-devscripts generic GHC postinst template
# End automatically added section
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;I think it should be possible to get &lt;code&gt;dh_haskell_prep&lt;/code&gt; to also generate the &lt;code&gt;libghc6-X-doc.post{inst,rm}&lt;/code&gt;.  To me that seems like an improvement that it&#039;d be very easy to sell to the maintainer of &lt;code&gt;haskell-devscripts&lt;/code&gt;.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>@Jeremy,</p>

<p>First of all, thanks for commenting on this at all <img src='http://therning.org/magnus/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>

<p>I think the best route is to get things into Debian.  The <code>haskell-devscripts</code> I have on my Sid system is maintained by Arjan Oosting though, not by John Goerzen.  I don&#8217;t know if I can help in any way in convincing the maintainer to include your changes, and ideally to also upload cabal-debian itself to Debian proper, but I&#8217;d be more than willing to chip in if you want me to.  Arjan, if you are reading this, please help out a poor Debian user here!  <img src='http://therning.org/magnus/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>

<p>I&#8217;ll try to explain what I mean with the second item.  During building of the package <code>dh_haskell_prep</code> is called and it generates two snippets, <code>libghc6-dataenc-dev.postinst.debhelper</code> and <code>libghc6-dataenc-dev.prerm.debhelper</code>.  The former has the following contents (taken from my use of cabal-debian on dataenc):</p>

<pre><code># Automatically added by dh_haskell_prep
GHC_PKG=/usr/lib/ghc-6.8.2/bin/ghc-pkg 
CONFIGFILE=/usr/lib/haskell-packages/ghc6/lib/dataenc-0.12/installed-pkg-config


case "$1" in
    abort-deconfigure|abort-remove|abort-upgrade|configure)
    OLDVERSIONS=`$GHC_PKG --global field dataenc version 2&gt; /dev/null | sed "s/version: //"`
    for VERSION in $OLDVERSIONS ; do
        $GHC_PKG --global hide dataenc-$VERSION || true
    done
    $GHC_PKG --global --auto-ghci-libs register $CONFIGFILE
    ;;
    *)
        echo "postinst called with unknown argument \`$1'" &gt;&amp;2
        exit 1
    ;;
esac



# arch-tag: haskell-devscripts generic GHC postinst template
# End automatically added section
</code></pre>

<p>I think it should be possible to get <code>dh_haskell_prep</code> to also generate the <code>libghc6-X-doc.post{inst,rm}</code>.  To me that seems like an improvement that it&#8217;d be very easy to sell to the maintainer of <code>haskell-devscripts</code>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Shaw</title>
		<link>http://therning.org/magnus/archives/485/comment-page-1#comment-169087</link>
		<dc:creator>Jeremy Shaw</dc:creator>
		<pubDate>Fri, 23 Jan 2009 02:57:41 +0000</pubDate>
		<guid isPermaLink="false">http://therning.org/magnus/?p=485#comment-169087</guid>
		<description><![CDATA[&lt;p&gt;You definitely have the right to feel frustrated, we have not really made things as obvious or accessible as they should be. I am working on correcting this.&lt;/p&gt;

&lt;p&gt;This first step is to get all the required packages uploaded to hackagedb.(The debian package on hackage is the right debian package, it&#039;s just version 1.x and you need 3.x. I uploaded a newer version but it failed to build, I am tracking that down now).&lt;/p&gt;

&lt;p&gt;The second step is to figure out what to do about haskell-devscripts-cdbs. The difficulty is that haskell-devscripts is maintained by John Goerzen in a git repo while hlibrary.mk is maintained by Kari Pahula in a darcs repository. We could host our own version of haskell-devscripts on src.seereason.com, which includes hlibrary.mk plus our changes, but then it will be hard for people to recognize that the version of haskell-devscripts in debian and ubuntu is not going to work. That was the supposed advantage of introducing a new package, haskell-devscripts-cdbs -- we could depend on a different package to ensure we got a version that had our changes.&lt;/p&gt;

&lt;p&gt;We had some discussion among ourselves today came up with one possibility:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;send our changes to haskell-devscripts back to J. Goerzen. They should not break any existing users of haskell-devscripts, and may in fact make things better.&lt;/li&gt;
&lt;li&gt;convince Kari Pahula to take our changes to hlibrary.mk and to also debianize hlibrary.mk in it&#039;s own debian package so that it can be installed system-wide.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I think the only issue is that we added some hooks to hlibrary.mk (and possibly haskell-devscripts) which are only used by cabal-debian, or which call cabal-debian. But I believe these hooks detect if cabal-debian is present and everything works normally if you don&#039;t have cabal-debian installed. So this should not have any negative implications for existing users of haskell-devscripts and hlibrary.mk.&lt;/p&gt;

&lt;p&gt;In any case, we need to divide the code up, and sweet talk the other maintainers.&lt;/p&gt;

&lt;p&gt;Regarding the seereason-keyring package -- that is an oversight. I will add seereason-keyring to the autobuilder for the debian repo. I will also let david comment on the freshness of the debian packages. We primarily use the ubuntu hardy stuff right now, but I know david tries to get everything built occasionally. I suspect that after he gets everything building with ghc 6.10 on ubuntu, he will also update debian.&lt;/p&gt;

&lt;p&gt;I am going to refrain from commenting on your second wishlist item, because I am not familiar with the internals of what is going on, so I don&#039;t really know what it means.&lt;/p&gt;

&lt;p&gt;Anyway, thanks for your feedback! I&#039;ll will keep you posted as we get things into shape.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;jeremy&lt;/li&gt;
&lt;/ul&gt;
]]></description>
		<content:encoded><![CDATA[<p>You definitely have the right to feel frustrated, we have not really made things as obvious or accessible as they should be. I am working on correcting this.</p>

<p>This first step is to get all the required packages uploaded to hackagedb.(The debian package on hackage is the right debian package, it&#8217;s just version 1.x and you need 3.x. I uploaded a newer version but it failed to build, I am tracking that down now).</p>

<p>The second step is to figure out what to do about haskell-devscripts-cdbs. The difficulty is that haskell-devscripts is maintained by John Goerzen in a git repo while hlibrary.mk is maintained by Kari Pahula in a darcs repository. We could host our own version of haskell-devscripts on src.seereason.com, which includes hlibrary.mk plus our changes, but then it will be hard for people to recognize that the version of haskell-devscripts in debian and ubuntu is not going to work. That was the supposed advantage of introducing a new package, haskell-devscripts-cdbs &#8212; we could depend on a different package to ensure we got a version that had our changes.</p>

<p>We had some discussion among ourselves today came up with one possibility:</p>

<ol>
<li>send our changes to haskell-devscripts back to J. Goerzen. They should not break any existing users of haskell-devscripts, and may in fact make things better.</li>
<li>convince Kari Pahula to take our changes to hlibrary.mk and to also debianize hlibrary.mk in it&#8217;s own debian package so that it can be installed system-wide.</li>
</ol>

<p>I think the only issue is that we added some hooks to hlibrary.mk (and possibly haskell-devscripts) which are only used by cabal-debian, or which call cabal-debian. But I believe these hooks detect if cabal-debian is present and everything works normally if you don&#8217;t have cabal-debian installed. So this should not have any negative implications for existing users of haskell-devscripts and hlibrary.mk.</p>

<p>In any case, we need to divide the code up, and sweet talk the other maintainers.</p>

<p>Regarding the seereason-keyring package &#8212; that is an oversight. I will add seereason-keyring to the autobuilder for the debian repo. I will also let david comment on the freshness of the debian packages. We primarily use the ubuntu hardy stuff right now, but I know david tries to get everything built occasionally. I suspect that after he gets everything building with ghc 6.10 on ubuntu, he will also update debian.</p>

<p>I am going to refrain from commenting on your second wishlist item, because I am not familiar with the internals of what is going on, so I don&#8217;t really know what it means.</p>

<p>Anyway, thanks for your feedback! I&#8217;ll will keep you posted as we get things into shape.</p>

<ul>
<li>jeremy</li>
</ul>
]]></content:encoded>
	</item>
</channel>
</rss>
