Send Beginners mailing list submissions to
beginners@haskell.org
To subscribe or unsubscribe via the World Wide Web, visit
http://www.haskell.org/mailman/listinfo/beginners
or, via email, send a message with subject or body 'help' to
beginners-requ...@haskell.org
You can reach the person managing the list at
beginners-ow...@haskell.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Beginners digest..."
Today's Topics:
1. Re: cabal install errors (Benjamin Edwards)
2. Re: cabal install errors (damodar kulkarni)
3. source code for "Generics for the Masses" (Michael Litchard)
4. Error compiling OpenGL tutorial part 2 (Darren Grant)
----------------------------------------------------------------------
Message: 1
Date: Wed, 15 Aug 2012 12:04:15 +0100
From: Benjamin Edwards <edwards.b...@gmail.com>
Subject: Re: [Haskell-beginners] cabal install errors
To: damodar kulkarni <kdamodar2...@gmail.com>
Cc: haskellbeginners <beginners@haskell.org>
Message-ID:
<can6k4nhm7rv3r9rudpprl7fpfpe_nawuwos3sjk26ndfmua...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Ironically enough, cabal is an acronym: Common Architecture for Building
Applications and Libraries. Look ma, no packages! It is shame that almost
every new-comer gets burnt by this in one way or another. I might have a
crack at suggesting some re-writes, or extra caveats to the cabal docs.
On Aug 15, 2012 5:39 AM, "damodar kulkarni" <kdamodar2...@gmail.com> wrote:
>
> Please see this:
>> http://ivanmiljenovic.wordpress.com/2010/03/15/repeat-after-me-cabal-is-not-a-package-manager/
>>
>
> it is unfortunately true that cabal documentation is very misleading to
> many, especially the beginners ...
> that's why so many of us need to repeat after-an-expert that
> cabal-is-not-a-package-manager ...
>
> But now take a look at how many times the cabal user guide mentions the
> term "package" in its documentation, it is very easy to get misled...
>
> Cabal specifies a standard way in which Haskell libraries and applications
>> can be *packaged* so that it is easy for consumers to use them, or *
>> re-package* them, regardless of the Haskell implementation or
>> installation platform.
>>
>> Cabal defines a common interface ? the *Cabal package* ? between *package
>> authors, builders and users*. There is a library to help package authors
>> implement this interface, and a tool to enable developers, builders and
>> users *to work with Cabal packages*.
>>
> taken from http://www.haskell.org/cabal/users-guide/
>
> cabal should have been called haskell-make or hmake or something alike...
>
> thanks Benjamin, for the cabal-dev, hsenv tip though.
>
> -Damodar
>
>
> On Tue, Aug 14, 2012 at 5:38 PM, Benjamin Edwards
> <edwards.b...@gmail.com>wrote:
>
>> I think one point bears repeating: cabal is a build system, really. It
>> does a good enough job of that. It is a *terrible* package manager and
>> using it as one I think is a classic mistake that the community needs to
>> address.
>>
>> My two-penneth worth is this:
>>
>> Use cabal-dev, or hsenv, for *everything* and 99% of your woes will go
>> away. The the only thing I do when getting haskell up and running is to get
>> cabal-dev installed and it's dependencies in the cabal per user pkg store
>> and then cabal-dev sandboxes for everything from then on.
>> On Aug 14, 2012 11:57 AM, "Carlos J. G. Duarte" <
>> carlos.j.g.dua...@gmail.com> wrote:
>>
>>> On 08/13/12 22:19, Gregory Guthrie wrote:
>>>
>>> Thanks, I'll try that, but it looks like it could be a lot of maintenance
>>> and manual cleanup!
>>>
>>> I haven't knowingly done any manual upgrades of core packages, but I have
>>> done "update"s as asked by cabal when it thinks the database is getting
>>> old. I have had such pedestrian usage that I would not have expected to
>>> have goofed up the database! :-)
>>>
>>> Cabal seems to be more troublesome that other various *package managers*
>>> like apt, etc...
>>>
>>>
>>> Please see this:
>>> http://ivanmiljenovic.wordpress.com/2010/03/15/repeat-after-me-cabal-is-not-a-package-manager/
>>>
>>> But yes, cabal or not, I agree that there should be a better system for
>>> managing haskell packages, like pip, gem or cpan... but that boils down to
>>> the problem that some has to do it, and people who are able to do it** are
>>> often too busy for that.
>>>
>>> ** and that doesn't include me, as I'm just starting to explore Haskell
>>> on my spare time.
>>>
>>> All in all, cabal suits me even with its idiosyncrasies.
>>>
>>>
>>> _______________________________________________
>>> Beginners mailing list
>>> Beginners@haskell.org
>>> http://www.haskell.org/mailman/listinfo/beginners
>>>
>>>
>> _______________________________________________
>> Beginners mailing list
>> Beginners@haskell.org
>> http://www.haskell.org/mailman/listinfo/beginners
>>
>>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.haskell.org/pipermail/beginners/attachments/20120815/09e28ac3/attachment-0001.htm>
------------------------------
Message: 2
Date: Wed, 15 Aug 2012 21:36:42 +0530
From: damodar kulkarni <kdamodar2...@gmail.com>
Subject: Re: [Haskell-beginners] cabal install errors
To: Benjamin Edwards <edwards.b...@gmail.com>
Cc: haskellbeginners <beginners@haskell.org>
Message-ID:
<CAD5HsypvF0iKeOpSUheowOP=ubgpuhdsgkfsflgjoiub0z9...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Thanks for the clarification.
BTW, is PACKAGE too an acronym?
So, what can we say about cabal and cabal-doc?
The name CABAL poses no problem (after all it is but a name, acronym or
not) BUT (and it is a very big but)
the cabal documentation seems to tell users about "packages and package
management issues" from the very start AND still the experts seem to expect
from the beginners that the beginners SHOULD ignore this fact and should go
figure out what the real thing the cabal is supposed to do!!!
I think, it will be much better if the first thing the NEW cabal doc to
have is a link to the
http://ivanmiljenovic.wordpress.com/2010/03/15/repeat-after-me-cabal-is-not-a-package-manager/
regards,
-damodar
On Wed, Aug 15, 2012 at 4:34 PM, Benjamin Edwards <edwards.b...@gmail.com>wrote:
> Ironically enough, cabal is an acronym: Common Architecture for Building
> Applications and Libraries. Look ma, no packages! It is shame that almost
> every new-comer gets burnt by this in one way or another. I might have a
> crack at suggesting some re-writes, or extra caveats to the cabal docs.
> On Aug 15, 2012 5:39 AM, "damodar kulkarni" <kdamodar2...@gmail.com>
> wrote:
>
>>
>> Please see this:
>>> http://ivanmiljenovic.wordpress.com/2010/03/15/repeat-after-me-cabal-is-not-a-package-manager/
>>>
>>
>> it is unfortunately true that cabal documentation is very misleading to
>> many, especially the beginners ...
>> that's why so many of us need to repeat after-an-expert that
>> cabal-is-not-a-package-manager ...
>>
>> But now take a look at how many times the cabal user guide mentions the
>> term "package" in its documentation, it is very easy to get misled...
>>
>> Cabal specifies a standard way in which Haskell libraries and
>>> applications can be *packaged* so that it is easy for consumers to use
>>> them, or *re-package* them, regardless of the Haskell implementation or
>>> installation platform.
>>>
>>> Cabal defines a common interface ? the *Cabal package* ? between *package
>>> authors, builders and users*. There is a library to help package
>>> authors implement this interface, and a tool to enable developers, builders
>>> and users *to work with Cabal packages*.
>>>
>> taken from http://www.haskell.org/cabal/users-guide/
>>
>> cabal should have been called haskell-make or hmake or something alike...
>>
>> thanks Benjamin, for the cabal-dev, hsenv tip though.
>>
>> -Damodar
>>
>>
>> On Tue, Aug 14, 2012 at 5:38 PM, Benjamin Edwards <edwards.b...@gmail.com
>> > wrote:
>>
>>> I think one point bears repeating: cabal is a build system, really. It
>>> does a good enough job of that. It is a *terrible* package manager and
>>> using it as one I think is a classic mistake that the community needs to
>>> address.
>>>
>>> My two-penneth worth is this:
>>>
>>> Use cabal-dev, or hsenv, for *everything* and 99% of your woes will go
>>> away. The the only thing I do when getting haskell up and running is to get
>>> cabal-dev installed and it's dependencies in the cabal per user pkg store
>>> and then cabal-dev sandboxes for everything from then on.
>>> On Aug 14, 2012 11:57 AM, "Carlos J. G. Duarte" <
>>> carlos.j.g.dua...@gmail.com> wrote:
>>>
>>>> On 08/13/12 22:19, Gregory Guthrie wrote:
>>>>
>>>> Thanks, I'll try that, but it looks like it could be a lot of maintenance
>>>> and manual cleanup!
>>>>
>>>> I haven't knowingly done any manual upgrades of core packages, but I have
>>>> done "update"s as asked by cabal when it thinks the database is getting
>>>> old. I have had such pedestrian usage that I would not have expected to
>>>> have goofed up the database! :-)
>>>>
>>>> Cabal seems to be more troublesome that other various *package managers*
>>>> like apt, etc...
>>>>
>>>>
>>>> Please see this:
>>>> http://ivanmiljenovic.wordpress.com/2010/03/15/repeat-after-me-cabal-is-not-a-package-manager/
>>>>
>>>> But yes, cabal or not, I agree that there should be a better system for
>>>> managing haskell packages, like pip, gem or cpan... but that boils down to
>>>> the problem that some has to do it, and people who are able to do it** are
>>>> often too busy for that.
>>>>
>>>> ** and that doesn't include me, as I'm just starting to explore Haskell
>>>> on my spare time.
>>>>
>>>> All in all, cabal suits me even with its idiosyncrasies.
>>>>
>>>>
>>>> _______________________________________________
>>>> Beginners mailing list
>>>> Beginners@haskell.org
>>>> http://www.haskell.org/mailman/listinfo/beginners
>>>>
>>>>
>>> _______________________________________________
>>> Beginners mailing list
>>> Beginners@haskell.org
>>> http://www.haskell.org/mailman/listinfo/beginners
>>>
>>>
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.haskell.org/pipermail/beginners/attachments/20120815/084670ba/attachment-0001.htm>
------------------------------
Message: 3
Date: Wed, 15 Aug 2012 17:03:38 -0700
From: Michael Litchard <mich...@schmong.org>
Subject: [Haskell-beginners] source code for "Generics for the Masses"
To: beginners@haskell.org
Message-ID:
<caezekypk9dxoz_z9ftl0jc0rjixscnve-yrk9zdz3dbeh_x...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
In the paper by Ralf Hinze, "Generics for the Masses", there is
reference to code one may play with. But the link,
http://www.ralf-hinze.de/masses.tar.bz2 is dead. I know someone,
somewhere has this file. Could you point me to where it lives?
------------------------------
Message: 4
Date: Thu, 16 Aug 2012 00:16:20 -0700
From: Darren Grant <therealklu...@gmail.com>
Subject: [Haskell-beginners] Error compiling OpenGL tutorial part 2
To: beginners@haskell.org
Message-ID:
<CA+jD6ShyerLAQyQG-bYu=oVrKV3RCNWCx=QtJxULt22Me=-m...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
I am currently following the OpenGL tutorial here:
http://www.haskell.org/haskellwiki/OpenGLTutorial2
But in the current incarnation of Display.hs
(http://pastebin.com/g4NekDVh) I am getting the following error:
$ cabal install
Resolving dependencies...
Configuring mygl-0.1...
Preprocessing executables for mygl-0.1...
Building mygl-0.1...
[3 of 5] Compiling Display ( Display.hs,
dist\build\mygl\mygl-tmp\Display.o )
Display.hs:13:9:
Couldn't match expected type `IO a0' with actual type `()'
In the return type of a call of `mapM_'
In a stmt of a 'do' expression:
mapM_
(\ (x, y, z)
-> preservingMatrix
$ do { color
$ Color3 ((x + 1.0) / 2.0) ((y + 1.0) / 2.0) ((z +
1.0) / 2.0);
translate $ Vector3 x y z;
cube (0.1 :: GLfloat) })
points
7
In the expression:
do { clear [ColorBuffer];
scale 0.7 0.7 (0.7 :: GLfloat);
mapM_
(\ (x, y, z)
-> preservingMatrix
$ do { color
$ Color3 ((x + 1.0) / 2.0) ((y + 1.0) / 2.0) ((z
+ 1.0) / 2.0);
.... })
points
7;
flush }
cabal.exe: Error: some packages failed to install:
mygl-0.1 failed during the building phase. The exception was:
ExitFailure 1
Not being too familiar with the Haskell syntax I'm not sure how to go
about decomposing the code to find the source of the problem.
Is there any general advice that might help me with this sort of situation?
Thank you!
------------------------------
_______________________________________________
Beginners mailing list
Beginners@haskell.org
http://www.haskell.org/mailman/listinfo/beginners
End of Beginners Digest, Vol 50, Issue 17
*****************************************
