On Mar 15, 2013, at 5:33 PM, Jason Dagit dag...@gmail.com wrote:
I was going to start making these changes and I noticed that it doesn't
currently build with ghc 7.4.1 w/Haskell Platform:
https://travis-ci.org/dagit/lambdabot/builds/5541375
Do you know if the constraints on:
On Mar 15, 2013, at 5:33 PM, Jason Dagit dag...@gmail.com wrote:
Do you know if the constraints on:
regex-posix-0.95.1
regex-compat-0.95.1
Need to be what they are? Could we relax them without breaking anything?
The constraints were added recently, and I believe they were a very
On Wed, Feb 20, 2013 at 11:19 AM, Gwern Branwen gwe...@gmail.com wrote:
On Wed, Feb 20, 2013 at 1:35 PM, Jan Stolarek jan.stola...@p.lodz.pl
wrote:
Gwern, and what do you think about James' fork of lambdabot? It seems
that there was a lot of work
put into it and that this is indeed a good
On Mar 14, 2013, at 11:08 PM, Jason Dagit dag...@gmail.com wrote:
My real reason for reviving this thread: Can I get a status update, please?
Sure. I don't have as much time as I'd like these days for open-source
projects, but with Jan's help the code has been cleaned up quite a bit in
On Fri, Mar 15, 2013 at 9:19 AM, James Cook mo...@deepbondi.net wrote:
On Mar 14, 2013, at 11:08 PM, Jason Dagit dag...@gmail.com wrote:
My real reason for reviving this thread: Can I get a status update,
please?
Sure. I don't have as much time as I'd like these days for open-source
On Mar 15, 2013, at 2:45 PM, Jason Dagit dag...@gmail.com wrote:
I haven't been following the thread closely. Is there also a github? If so,
where? Some of us figured out a bug fix for the quotes plugin and I'll send a
pull request if I get a chance.
Yep, there is[1]. I'm not sure what the
On Fri, Mar 15, 2013 at 3:30 PM, James Cook mo...@deepbondi.net wrote:
On Mar 15, 2013, at 2:45 PM, Jason Dagit dag...@gmail.com wrote:
I haven't been following the thread closely. Is there also a github? If
so, where? Some of us figured out a bug fix for the quotes plugin and I'll
send a
On Fri, Mar 15, 2013 at 4:31 PM, Jason Dagit dag...@gmail.com wrote:
On Fri, Mar 15, 2013 at 3:30 PM, James Cook mo...@deepbondi.net wrote:
On Mar 15, 2013, at 2:45 PM, Jason Dagit dag...@gmail.com wrote:
I haven't been following the thread closely. Is there also a github? If
so, where?
On 20/02/13 08:13, Jan Stolarek wrote:
Dnia wtorek, 19 lutego 2013, Gwern Branwen napisał:
On Tue, Feb 19, 2013 at 5:36 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
- remove unlambda, brainfuck and show from the repo. They are on hackage,
no need to keep them here - these packages aren't
On Feb 19, 2013, at 9:54 PM, Jason Dagit dag...@gmail.com wrote:
Random thought, feel free to ignore it: Would it make sense to split
lambdabot up into core and contrib like is done with xmonad? Contrib could
contain the sillier things like bf, unlambda, show, etc and would have a
lower
Any opinion about whether it's better to put them
in the same or separate actual repos?
The general rule in git is that a repo should contain a single project. There
are some projects
that violate this rule - e.g. cabal stores both Cabal and cabal-install in the
same repository -
but with
Are you suggesting that the source code of these packages is moved out to
their own darcs repositories?
Exactly. This allows to use and develop these packages independently of
lambdabot and I consider
that a Good Thing. I'm also much in favor of using git, because github allows
easy
I've catalogued a list of issues on github:
https://github.com/mokus0/lambdabot/issues
Let me know if you have objections against any of them. If no then I will try
to fix them
gradually. Right now a major problem for me are exceptions in Data.Binary, but
I don't think I
will be able to fix
On Wed, Feb 20, 2013 at 12:59 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
Exactly. This allows to use and develop these packages independently of
lambdabot and I consider
that a Good Thing. I'm also much in favor of using git, because github allows
easy collaboration
between community
goodness may be outweighed by the costs of switching:
Could you specify what are those cost of switching?
Turns out the
reason for people not submitting patches had more to do with things
besides not being hosted on Github.
Of course. I don't clain this is the reason for people not
My 2 cents:
Switching to github: +0.1
Splitting into core contrib: +1
Okay I suppose that is more like 1.1 cents.
I would love to help maintain lambdabot and help brush off the bitrot, but
am personally quite overextended so I can't really promise any amount of
dedication for at least the next
On Wed, Feb 20, 2013 at 1:35 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
Gwern, and what do you think about James' fork of lambdabot? It seems that
there was a lot of work
put into it and that this is indeed a good starting point to continue
development.
I haven't looked at the diffs; if
I'm happy to hear your approval.
I've spent some time yesterday cleaning up the code and writing down all things
that do not work.
The list I made is avaliable on github:
https://github.com/killy/lambdabot/issues
There are 17 open issues at the moment and I know I will not have enough
For what it's worth, I also have a fork of lambdabot[1] I've been using for
quite a while now, which may provide a cleaner starting point. In particular,
it updates the plugin and command API to be (IMO) quite a bit cleaner and
easier to use and understand. It could probably use some
Wow, this indeed looks like a nice starting point, though I can't build
lambdabot from your repo -
seems that dice package is not on Hackage. Is this the package that you rely on:
https://github.com/serialhex/dice ?
Anyway, how would you feel about changes that I would like to make:
- move all
Sorry, I uploaded it this morning since I knew it wasn't there (it's the dice
repo from my github account, mokus0). Have you run cabal update in the last
4 or 5 hours?
On Feb 19, 2013, at 2:36 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
Wow, this indeed looks like a nice starting point,
On Tue, Feb 19, 2013 at 5:36 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
- remove unlambda, brainfuck and show from the repo. They are on hackage, no
need to keep them
here - these packages aren't even used in the build process.
Where will they go?
--
gwern
http://www.gwern.net
On Feb 19, 2013, at 2:36 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
Anyway, how would you feel about changes that I would like to make:
- move all modules into Lambdabot. namespace
- remove unlambda, brainfuck and show from the repo. They are on hackage, no
need to keep them
here -
On Tue, Feb 19, 2013 at 3:01 PM, James Cook mo...@deepbondi.net wrote:
On Feb 19, 2013, at 2:36 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
Anyway, how would you feel about changes that I would like to make:
- move all modules into Lambdabot. namespace
- remove unlambda, brainfuck and
Dnia wtorek, 19 lutego 2013, Gwern Branwen napisał:
On Tue, Feb 19, 2013 at 5:36 PM, Jan Stolarek jan.stola...@p.lodz.pl wrote:
- remove unlambda, brainfuck and show from the repo. They are on hackage,
no need to keep them here - these packages aren't even used in the build
process.
Where
I have no objections to any of these,
Great. Then I will start making mentioned changes and sending pull requests
when I find some free
time.
though I would recommend as Gwern
hinted that if related packages are to be removed that they should also be
given new homes - I believe that the
On Sun, Feb 17, 2013 at 8:53 PM, Cale Gibbard cgibb...@gmail.com wrote:
On 17 February 2013 18:03, Jan Stolarek jan.stola...@p.lodz.pl wrote:
...
This changes would be quite invasive and code wouldn't be compatible
with the lambdabot repo on
haskell.org. So before I start making any of
Hi all,
as some of you may have noticed Lambdabot doesn't build on GHC 7.6.1 due to
OldException being
removed (and a few other changes). I updated the code so that it builds on
latest GHC release.
The updated code is available here:
https://github.com/killy/lambdabot/tree/upstream
It
On 17 February 2013 18:03, Jan Stolarek jan.stola...@p.lodz.pl wrote:
...
This changes would be quite invasive and code wouldn't be compatible with the
lambdabot repo on
haskell.org. So before I start making any of them I would like to hear from
the community if such
changes in the source
Sounds great. Lambdabot is an important icon to the Haskell community; it
will be nice to brush off the bitrot and make lambdabot easier for the
average Haskeller to install without having to rely on Cale keeping it
running on irc (grateful, though we are).
-- Dan Burton
On Feb 17, 2013 3:04 PM,
30 matches
Mail list logo
