<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Installing Weblocks</title>
	<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/</link>
	<description>Dev related notes, tutorials and anecdotes</description>
	<pubDate>Sat, 22 Nov 2008 13:08:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Henrik</title>
		<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-348</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Sun, 06 Jan 2008 05:41:04 +0000</pubDate>
		<guid>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-348</guid>
		<description>I just downloaded the UCW boxset and it ran like a charm so I'll be back with some UCW stuff instead in the near future, finally I'm up and running! It's gonna be fun to see what all the fuss is about.

Download here: http://common-lisp.net/project/ucw/download.html</description>
		<content:encoded><![CDATA[<p>I just downloaded the UCW boxset and it ran like a charm so I&#8217;ll be back with some UCW stuff instead in the near future, finally I&#8217;m up and running! It&#8217;s gonna be fun to see what all the fuss is about.</p>
<p>Download here: <a href="http://common-lisp.net/project/ucw/download.html" rel="nofollow">http://common-lisp.net/project/ucw/download.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik</title>
		<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-1635</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Sun, 06 Jan 2008 05:41:04 +0000</pubDate>
		<guid>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-1635</guid>
		<description>I just downloaded the UCW boxset and it ran like a charm so I&#39;ll be back with some UCW stuff instead in the near future, finally I&#39;m up and running! It&#39;s gonna be fun to see what all the fuss is about.&lt;br&gt;&lt;br&gt;Download here: &lt;a href="http://common-lisp.net/project/ucw/download.html"&gt;http://common-lisp.net/project/ucw/download.html&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I just downloaded the UCW boxset and it ran like a charm so I&#39;ll be back with some UCW stuff instead in the near future, finally I&#39;m up and running! It&#39;s gonna be fun to see what all the fuss is about.</p>
<p>Download here: <a href="http://common-lisp.net/project/ucw/download.html">http://common-lisp.net/project/ucw/download.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik</title>
		<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-329</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Tue, 01 Jan 2008 10:55:36 +0000</pubDate>
		<guid>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-329</guid>
		<description>I redid the whole process with Ubuntu Feisty 64. I got through but when running (weblocks:start-weblocks) and trying to load the welcome page with http://localhost:8080/ I got nothing, just waiting for localhost...</description>
		<content:encoded><![CDATA[<p>I redid the whole process with Ubuntu Feisty 64. I got through but when running (weblocks:start-weblocks) and trying to load the welcome page with <a href="http://localhost:8080/" rel="nofollow">http://localhost:8080/</a> I got nothing, just waiting for localhost&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik</title>
		<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-1187</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Tue, 01 Jan 2008 10:55:36 +0000</pubDate>
		<guid>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-1187</guid>
		<description>I redid the whole process with Ubuntu Feisty 64. I got through but when running (weblocks:start-weblocks) and trying to load the welcome page with &lt;a href="http://localhost:8080/"&gt;http://localhost:8080/&lt;/a&gt; I got nothing, just waiting for localhost...</description>
		<content:encoded><![CDATA[<p>I redid the whole process with Ubuntu Feisty 64. I got through but when running (weblocks:start-weblocks) and trying to load the welcome page with <a href="http://localhost:8080/">http://localhost:8080/</a> I got nothing, just waiting for localhost&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivar Refsdal</title>
		<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-289</link>
		<dc:creator>Ivar Refsdal</dc:creator>
		<pubDate>Sat, 29 Dec 2007 11:44:46 +0000</pubDate>
		<guid>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-289</guid>
		<description>Thanks for a nice article.

I did exactly as you as well, and everything worked. Heh.
i got two/three warnings which you could continue, none in the second package though.

I'm running sbcl 1.0.2 (latest PPC MAC) from the official SBCL site.

Good luck with your next attempts...
I'll post more details if you like.</description>
		<content:encoded><![CDATA[<p>Thanks for a nice article.</p>
<p>I did exactly as you as well, and everything worked. Heh.<br />
i got two/three warnings which you could continue, none in the second package though.</p>
<p>I&#8217;m running sbcl 1.0.2 (latest PPC MAC) from the official SBCL site.</p>
<p>Good luck with your next attempts&#8230;<br />
I&#8217;ll post more details if you like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik</title>
		<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-257</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Fri, 28 Dec 2007 05:19:42 +0000</pubDate>
		<guid>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-257</guid>
		<description>Tried it, but damn: 
"Server responded 404 for GET http://www.cliki.net/cl-weblocks?download"

Will try again later today, hopefully I'll have better luck then. :)</description>
		<content:encoded><![CDATA[<p>Tried it, but damn:<br />
&#8220;Server responded 404 for GET <a href="http://www.cliki.net/cl-weblocks?download" rel="nofollow">http://www.cliki.net/cl-weblocks?download</a>&#8221;</p>
<p>Will try again later today, hopefully I&#8217;ll have better luck then. <img src='http://www.prodevtips.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik</title>
		<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-246</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Thu, 27 Dec 2007 16:21:29 +0000</pubDate>
		<guid>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-246</guid>
		<description>"just plain (asdf-install:install :cl-weblocks) should suffice"

Eh, what a total noob I fee like (and am). Still, a little common sense would have had me trying the above. Noobishnes is not really an excuse... Or did I read somewhere that weblocks was not asdf installable? I can't remember, maybe some old advice, have to check.

Ah I found it: http://trac.common-lisp.net/cl-weblocks/wiki/ObtainingAndInstalling

From that page:
&lt;blockquote&gt;
Weblocks is a very young piece of software. At the moment installing it is a little more difficult that necessary. While Weblocks is ASDF-aware, it is not currently ASDF-installable as there have been no formal releases.
&lt;/blockquote&gt;

Obviously wrong then, maybe it should be removed?

I'll definitely try it tomorrow, hopefully the version of metatilities that will be pulled by that line will differ somehow from the one you get when trying to install it independently?

Btw, thanks!</description>
		<content:encoded><![CDATA[<p>&#8220;just plain (asdf-install:install :cl-weblocks) should suffice&#8221;</p>
<p>Eh, what a total noob I fee like (and am). Still, a little common sense would have had me trying the above. Noobishnes is not really an excuse&#8230; Or did I read somewhere that weblocks was not asdf installable? I can&#8217;t remember, maybe some old advice, have to check.</p>
<p>Ah I found it: <a href="http://trac.common-lisp.net/cl-weblocks/wiki/ObtainingAndInstalling" rel="nofollow">http://trac.common-lisp.net/cl-weblocks/wiki/ObtainingAndInstalling</a></p>
<p>From that page:</p>
<blockquote><p>
Weblocks is a very young piece of software. At the moment installing it is a little more difficult that necessary. While Weblocks is ASDF-aware, it is not currently ASDF-installable as there have been no formal releases.
</p></blockquote>
<p>Obviously wrong then, maybe it should be removed?</p>
<p>I&#8217;ll definitely try it tomorrow, hopefully the version of metatilities that will be pulled by that line will differ somehow from the one you get when trying to install it independently?</p>
<p>Btw, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose Ramirez</title>
		<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-245</link>
		<dc:creator>Jose Ramirez</dc:creator>
		<pubDate>Thu, 27 Dec 2007 15:53:23 +0000</pubDate>
		<guid>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-245</guid>
		<description>just linking the .asd files into a dir that is mentioned in central registry is sufficient (asdf-install under sbl creates a .sbcl dir in home, containing two dirs : site and systems. Source codes are kept in directories under system and all relevant .asd files are linked into the systems dir.

also, as all of the dependencies are asdf-installable, just plain (asdf-install:install :cl-weblocks) should suffice (all known dependencies are pulled in as necessary).

If you wanna see dependency hell, look at uncommon web (or worse yet, lisp on lines ;-), bajillion of libs, half of them in a custom-patched versions ...</description>
		<content:encoded><![CDATA[<p>just linking the .asd files into a dir that is mentioned in central registry is sufficient (asdf-install under sbl creates a .sbcl dir in home, containing two dirs : site and systems. Source codes are kept in directories under system and all relevant .asd files are linked into the systems dir.</p>
<p>also, as all of the dependencies are asdf-installable, just plain (asdf-install:install :cl-weblocks) should suffice (all known dependencies are pulled in as necessary).</p>
<p>If you wanna see dependency hell, look at uncommon web (or worse yet, lisp on lines ;-), bajillion of libs, half of them in a custom-patched versions &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose Ramirez</title>
		<link>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-1186</link>
		<dc:creator>Jose Ramirez</dc:creator>
		<pubDate>Thu, 27 Dec 2007 15:53:23 +0000</pubDate>
		<guid>http://www.prodevtips.com/2007/12/25/weblocks-install-howto/#comment-1186</guid>
		<description>just linking the .asd files into a dir that is mentioned in central registry is sufficient (asdf-install under sbl creates a .sbcl dir in home, containing two dirs : site and systems. Source codes are kept in directories under system and all relevant .asd files are linked into the systems dir.&lt;br&gt;&lt;br&gt;also, as all of the dependencies are asdf-installable, just plain (asdf-install:install :cl-weblocks) should suffice (all known dependencies are pulled in as necessary).&lt;br&gt;&lt;br&gt;If you wanna see dependency hell, look at uncommon web (or worse yet, lisp on lines ;-), bajillion of libs, half of them in a custom-patched versions ...</description>
		<content:encoded><![CDATA[<p>just linking the .asd files into a dir that is mentioned in central registry is sufficient (asdf-install under sbl creates a .sbcl dir in home, containing two dirs : site and systems. Source codes are kept in directories under system and all relevant .asd files are linked into the systems dir.</p>
<p>also, as all of the dependencies are asdf-installable, just plain (asdf-install:install :cl-weblocks) should suffice (all known dependencies are pulled in as necessary).</p>
<p>If you wanna see dependency hell, look at uncommon web (or worse yet, lisp on lines ;-), bajillion of libs, half of them in a custom-patched versions &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
