On 2 November 2011 01:08, Diego Souza dso...@bitforest.org wrote:
The idea is simple: there are many different platforms that would be
to expensive for one to support. So they ask the community for help,
and then distribute the load amongst the perl community.
Duncan and co have been working
Yitzchak Gale g...@sefer.org writes:
Gregory Crosswhite wrote:
could [Hackage] have a feature where when a
working package breaks with a new version of
GHC the author is automatically e-mailed?
This would be nice. However, there would have to be
a way for it to be turned on and off by the
On 1 November 2011 03:43, Alexander Kjeldaas
alexander.kjeld...@gmail.com wrote:
On 31 October 2011 17:22, Yitzchak Gale g...@sefer.org wrote:
Gregory Crosswhite wrote:
could [Hackage] have a feature where when a
working package breaks with a new version of
GHC the author is
On 1 November 2011 09:00, Ketil Malde ke...@malde.org wrote:
This is where it stranded the last time, IIRC. That sentiment makes me
a bit uneasy; so you are the official maintainer of a package on
Hackage, but you do not want to hear about it when it fails to compile?
Don't forget that some
On Tue, Nov 1, 2011 at 09:43, Conrad Parker con...@metadecks.org wrote:
On 1 November 2011 03:43, Alexander Kjeldaas
alexander.kjeld...@gmail.com wrote:
On 31 October 2011 17:22, Yitzchak Gale g...@sefer.org wrote:
Gregory Crosswhite wrote:
could [Hackage] have a feature where when a
I wrote:
This would be nice. However, there would have to be
a way for it to be turned on and off by the author.
(Spam is not nice.)
Ketil Malde wrote:
This is where it stranded the last time, IIRC. That sentiment makes me
a bit uneasy; so you are the official maintainer of a package on
Max Bolingbroke batterseapo...@hotmail.com writes:
This is where it stranded the last time, IIRC. That sentiment makes me
a bit uneasy; so you are the official maintainer of a package on
Hackage, but you do not want to hear about it when it fails to compile?
Don't forget that some packages
On 1 November 2011 10:14, Ketil Malde ke...@malde.org wrote:
So, I'd *love* to get an email when my packages fail to build, but I will
accept that other people have a more sensitive relationship with their
inbox. (I assume that the people who raise this objection - Max
and Yitzchak - belong
On Tue, Nov 1, 2011 at 06:14, Ketil Malde ke...@malde.org wrote:
Max Bolingbroke batterseapo...@hotmail.com writes:
This is where it stranded the last time, IIRC. That sentiment makes me
a bit uneasy; so you are the official maintainer of a package on
Hackage, but you do not want to hear
Yitzchak Gale g...@sefer.org writes:
I am just a little worried that if uploading to Hackage
requires agreeing to unlimited uncontrollable
spamming by a bot,
The bot would, of course, be implemented in Haskell. Anybody who still
worries about bugs, is free to implement a better one in Agda.
On 1 November 2011 21:35, Ketil Malde ke...@malde.org wrote:
or even
Maintainer: Ketil Malde ketil at malde dot org -- email me if you are
human
Though unless the hackage email bot is smart enough, this will result
in a lot of unsendable emails...
--
Ivan Lazar Miljenovic
On 1 November 2011 21:35, Ketil Malde ke...@malde.org wrote:
or even
Maintainer: Ketil Malde ketil at malde dot org -- email me if you
are human
Though unless the hackage email bot is smart enough, this will result
in a lot of unsendable emails...
But the bot is not a human, so that's
How about to a new optional Cabal field like mail-report? (don't bother
about this name, I chose it randomly)
If a build failure happens, or there is some relevant information about
your package, Hackage will send a mail to the direction specified in that
field. A field which content will NOT
On 2011-11-01 12:59 +0100, Daniel Díaz Casanueva wrote:
How about to a new optional Cabal field like mail-report? (don't bother
about this name, I chose it randomly)
If a build failure happens, or there is some relevant information about
your package, Hackage will send a mail to the
On Tue, Nov 1, 2011 at 08:24, Nick Bowler nbow...@elliptictech.com wrote:
On 2011-11-01 12:59 +0100, Daniel Díaz Casanueva wrote:
How about to a new optional Cabal field like mail-report? (don't bother
about this name, I chose it randomly)
Doing anything like this in the .cabal file is a
Then, the mailing list seems to be an option. But then I will receive mails
for every package, and there is a lot of packages! Is not a lot of mails
this? There is another work around?
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
Daniel Díaz Casanueva writes:
How about to a new optional Cabal field like mail-report? (don't bother
about this name, I chose it randomly)
If a build failure happens, or there is some relevant information about your
package, Hackage will send a mail to the direction specified in that
On Nov 1, 2011 8:45 PM, Daniel Díaz Casanueva dhelta.d...@gmail.com
wrote:
Then, the mailing list seems to be an option. But then I will receive
mails for every package, and there is a lot of packages! Is not a lot of
mails this? There is another work around?
Nobody would read every build
On Tue, Nov 1, 2011 at 2:45 AM, Max Bolingbroke
batterseapo...@hotmail.com wrote:
On 1 November 2011 09:00, Ketil Malde ke...@malde.org wrote:
This is where it stranded the last time, IIRC. That sentiment makes me
a bit uneasy; so you are the official maintainer of a package on
Hackage, but
Ross A field in the .cabal file is just as available to bots as
Ross a field on the package page.
Yes, absolutly. There are at least one easy solution for this problem :
having a server-side user model that is related to packages, or to
packages versions, indicating wich user is the maintainer
The perl community has something really interesting for quite long time:
http://wiki.cpantesters.org/wiki/HomePage
Or more specifically:
http://matrix.cpantesters.org/?dist=DBI
The idea is simple: there are many different platforms that would be
to expensive for one to support. So they ask the
Hey everyone,
I have uploaded a number of small packages to Hackage that I no longer actively
use so that I don't find out immediately when a new version of GHC has broken
them. Since Hackage is going to the trouble of finding out when a package no
longer builds anyway, could it have a
On Mon, Oct 31, 2011 at 12:08 AM, Gregory Crosswhite
gcrosswh...@gmail.comwrote:
I have uploaded a number of small packages to Hackage that I no longer
actively use so that I don't find out immediately when a new version of GHC
has broken them. Since Hackage is going to the trouble of finding
Gregory Crosswhite wrote:
could [Hackage] have a feature where when a
working package breaks with a new version of
GHC the author is automatically e-mailed?
This would be nice. However, there would have to be
a way for it to be turned on and off by the author.
(Spam is not nice.)
Thanks,
Yitz
On 31 October 2011 17:22, Yitzchak Gale g...@sefer.org wrote:
Gregory Crosswhite wrote:
could [Hackage] have a feature where when a
working package breaks with a new version of
GHC the author is automatically e-mailed?
This would be nice. However, there would have to be
a way for it to
25 matches
Mail list logo
