On Tue, Dec 20, 2011 at 03:31, Fabio Riga wrote:
> Hi Magnus,
>
> sorry for my late answer on this and for my bad English... I'll try to be
> more clear.
>
> IMHO, the ArchHaskell project should be a very big repository with most
> up-to-date packages from hackage. Now, it seems to me that you are
Hi Magnus,
sorry for my late answer on this and for my bad English... I'll try to be
more clear.
IMHO, the ArchHaskell project should be a very big repository with most
up-to-date packages from hackage. Now, it seems to me that you are doing
all the work, so it's not possible for this project to
On 2011-Nov-10, Felipe Almeida Lessa wrote:
> On Thu, Nov 10, 2011 at 7:07 PM, Magnus Therning wrote:
> > So, what are our options when it comes to deciding what's in and
> > what's out? Any thoughts?
>
> One possibility is looking at the most downloaded packages on Hackage.
>
...
Are the d
On Sun, Nov 13, 2011 at 19:27, Bernardo Barros
wrote:
> Yes, disown those broken/outdated packages so other people can fix them...
I will, as soon as I have looked at some ways to disown that many
packages conveniently.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag.
On Sun, Nov 13, 2011 at 18:11, Fabio Riga wrote:
> Hello,
> 2011/11/12 Magnus Therning
>>
>> It would be excellent if more people could work on keeping [haskell]
>> up-to-date :)
>>
>> However, splitting updating the database and the building of packages
>> is likely to be a bit painful. So far
Yes, disown those broken/outdated packages so other people can fix them...
___
arch-haskell mailing list
arch-haskell@haskell.org
http://www.haskell.org/mailman/listinfo/arch-haskell
Regarding what to put in the repository, I would use AUR and aurvote. I
(and whoever want to) could maintain some aur package orphaned by
archhaskell user. Packages that take some vote go in arch-haskell. I don't
know how many people use yaourt, but I do and I would like to have as many
updated has
Hello,
2011/11/12 Magnus Therning
>
> It would be excellent if more people could work on keeping [haskell]
> up-to-date :)
>
> However, splitting updating the database and the building of packages
> is likely to be a bit painful. So far my experience is that updating
> packages to a buildable s
On Fri, Nov 11, 2011 at 11:12 PM, Magnus Therning wrote:
> On Fri, Nov 11, 2011 at 10:50:03PM +0100, Nicolas Pouillard wrote:
>> On Fri, Nov 11, 2011 at 10:40 PM, Magnus Therning
>> wrote:
>>> On Fri, Nov 11, 2011 at 10:26:54PM +0100, Nicolas Pouillard wrote:
On Fri, Nov 11, 2011 at 9:42 PM
On Fri, Nov 11, 2011 at 07:07:26PM -0800, Leif Warner wrote:
> On Thu, Nov 10, 2011 at 1:07 PM, Magnus Therning wrote:
>
>> Now we have 300+ packages in [haskell]. It's starting to be a large
>> set, and the time required to build when something changes is starting
>> to really be felt now. So I
On Fri, Nov 11, 2011 at 06:28:25PM -0800, Bernardo Barros wrote:
> But "arch-haskell" is supposed to be the maintainer of qtHaskell, at
> least on AUR. Are you going to disown it in AUR?
I'm guessing the package was created manually then. I will disown it.
/M
--
Magnus Therning
On Thu, Nov 10, 2011 at 1:07 PM, Magnus Therning wrote:
> Now we have 300+ packages in [haskell]. It's starting to be a large
> set, and the time required to build when something changes is starting
> to really be felt now. So I would like to start a discussion on how we
> should decide what crit
But "arch-haskell" is supposed to be the maintainer of qtHaskell, at
least on AUR. Are you going to disown it in AUR?
BTW, it is currently it is broken for me.
___
arch-haskell mailing list
arch-haskell@haskell.org
http://www.haskell.org/mailman/listinf
On Fri, Nov 11, 2011 at 01:07:17PM -0800, Bernardo Barros wrote:
> An automatic and distributed building and testing system would he
> useful here.
Indeed, and of course it should be gratis to use too ;)
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org
On Fri, Nov 11, 2011 at 10:26:54PM +0100, Nicolas Pouillard wrote:
> On Fri, Nov 11, 2011 at 9:42 PM, Magnus Therning wrote:
[...]
>>> Moreover I'm not fond of this kind of race.
>>
>> Neither am I, but I see no way easy way of addressing that.
>
> A way to quickly sending notices that a change i
On Thu, Nov 10, 2011 at 02:31:54PM -0800, Bernardo Barros wrote:
> Drop Agda and adopt Leksah and qtHaskell. =)
Unfortunately neither is likely to happen as it is right now:
- Leksah is even more of a pain than Agda, due to the amazingly long
list of dependencies and the upstream maintainers la
On Fri, Nov 11, 2011 at 06:37:14PM +0100, Nicolas Pouillard wrote:
>On Thu, Nov 10, 2011 at 10:07 PM, Magnus Therning wrote:
>> Now we have 300+ packages in [haskell]. It's starting to be a
>> large set, and the time required to build when something changes is
>> starting to really be felt now. S
On Thu, Nov 10, 2011 at 10:07 PM, Magnus Therning wrote:
> Now we have 300+ packages in [haskell]. It's starting to be a large
> set, and the time required to build when something changes is starting
> to really be felt now. So I would like to start a discussion on how we
> should decide what cri
Drop Agda and adopt Leksah and qtHaskell. =)
___
arch-haskell mailing list
arch-haskell@haskell.org
http://www.haskell.org/mailman/listinfo/arch-haskell
On Thu, Nov 10, 2011 at 7:07 PM, Magnus Therning wrote:
> So, what are our options when it comes to deciding what's in and
> what's out? Any thoughts?
One possibility is looking at the most downloaded packages on Hackage.
> Oh, and can I please drop Agda in the meantime? ;)
Fine for me =).
I'
Now we have 300+ packages in [haskell]. It's starting to be a large
set, and the time required to build when something changes is starting
to really be felt now. So I would like to start a discussion on how we
should decide what criteria to use when adding a package, and equally
important, what cr
21 matches
Mail list logo
