On Mon, Jun 27, 2011 at 12:00:21AM +0200, Fabio Riga wrote:
> Hi Magnus,
>
> I will also try your tool. Thanks for the advice.
Please let me know how you get on with it. You can report any bugs
straight to my email, as I still haven't gotten around to uploading
the source to github.
/M
--
Mag
Hi Fabio,
> Note that I tried makeworld script and rsync failed to connect to
> andromeda.kiwilight.com but I can ping the server.
the rsync server was down, apparently, but Kaiting has fixed the
problem. Rsync should now work fine.
Take care,
Peter
__
On Mon, Jun 27, 2011 at 12:51:18AM +0200, Peter Simons wrote:
> Hi Magnus,
>
> > Isn't this still the same workflow you had when you wrote [1]?
>
> no, it's not.
Since I'm curious, what improvements have you made to the tools that
address the inadequacy you reported back then?
Have they just b
Hi peter,
2011/6/27 Peter Simons :
> why do you assume that your builds would be faster than makeworld?
now that I looked into the scripts, I understand that I'm quite wrong
about time consuming: after the first time, it should be just the
same. Sorry for the silly assumption.
I'll wait for maki
Hi Leif,
> Should we put these instructions up on the README of the GitHub project
> for HABS / ArchHaskell ?
you are right, we probably should. I didn't do it at the time, because I
had the impression that various contributors were using all kinds of
different ways to work on HABS, and I didn'
Hi Magnus,
> Isn't this still the same workflow you had when you wrote [1]?
no, it's not.
Take care,
Peter
___
arch-haskell mailing list
arch-haskell@haskell.org
http://www.haskell.org/mailman/listinfo/arch-haskell
Hi Fabio,
> Packages must be tested. Before updating AUR I would compile the
> needed dependencies and only that, faster then makeword.
why do you assume that your builds would be faster than makeworld?
>> I'll try to describe my work-flow briefly: [...]
>
> The work flow can feet, but kno
Hi Magnus,
I will also try your tool. Thanks for the advice.
Cheers
Fabio
2011/6/26 Magnus Therning :
> I've written a tool called cblrepo[1] which aims to make it possible
> to maintain a consistent set of packages without having to rebuild
> to find broken dependencies. It is currently not us
Hi Peter,
2011/6/26 Peter Simons :
> > 1) In order to test for broken packages, do I really need to use the
> > makeworld script? I think it would take too much time!
>
> Unfortunately, distributing Haskell packages is a fairly complicated
> affair, mostly because these packages interact with ea
On Sun, Jun 26, 2011 at 05:39:54PM +0200, Peter Simons wrote:
> I'll try to describe my work-flow briefly:
[...]
> It's a bit of a mess, but it works okay. :-)
Isn't this still the same workflow you had when you wrote [1]?
/M
[1] http://www.haskell.org/pipermail/arch-haskell/2011-January/000865.
On Sun, Jun 26, 2011 at 8:39 AM, Peter Simons wrote:
>
> I'll try to describe my work-flow briefly:
>
> 1) Clone the 'peti/arch-haskell' repository.
>
> 2) Run "git submodules init" to set-up the HABS tree.
>
> 3) Run "cabal update" to download the latest database from hackage.
>
> 4) Run "ma
On Sun, Jun 26, 2011 at 04:37:53PM +0200, Fabio Riga wrote:
> Hi all,
>
> yesterday I submitted a patch to HABS repository just because I met
> some out-of-date packages in AUR. Then I read the "story" of this
> group in this mailing list and thought that I can give some help. I
> think I can take
Hi Fabio,
> yesterday I submitted a patch to HABS repository just because I met
> some out-of-date packages in AUR. Then I read the "story" of this
> group in this mailing list and thought that I can give some help. I
> think I can take responsibility for a bunch of packages and care for
> up
Hi all,
yesterday I submitted a patch to HABS repository just because I met
some out-of-date packages in AUR. Then I read the "story" of this
group in this mailing list and thought that I can give some help. I
think I can take responsibility for a bunch of packages and care for
updates, but I need
14 matches
Mail list logo
