Re: [haskell art] haskell in several upcoming live performances in the UK
Ugh, really bad mistake on my part, Anny! So sorry for my omission! All the more reason for Haskell people to come down to Brighton. On Jul 2, 2014 7:41 PM, "Anny" wrote: > I will be performing in Tidal-Haskell at the Brighton algorave this > weekend, FWIW. It should be nice to finally meet some of the livecoding > community for the first time after having "worked from home" so far. > -- > > Read the whole topic here: Haskell Art: > http://lurk.org/r/topic/5F8Ro3EhADavf0LVOI607L > > To leave Haskell Art, email haskell-...@group.lurk.org with the following > email subject: unsubscribe > -- Read the whole topic here: Haskell Art: http://lurk.org/r/topic/4QTo74RorShXKPCYeaYheH To leave Haskell Art, email haskell-...@group.lurk.org with the following email subject: unsubscribe
Re: [haskell art] haskell in several upcoming live performances in the UK
I will be performing in Tidal-Haskell at the Brighton algorave this weekend, FWIW. It should be nice to finally meet some of the livecoding community for the first time after having "worked from home" so far. -- Read the whole topic here: Haskell Art: http://lurk.org/r/topic/5F8Ro3EhADavf0LVOI607L To leave Haskell Art, email haskell-...@group.lurk.org with the following email subject: unsubscribe
Re: [haskell art] haskell in several upcoming live performances in the UK
Hi Renick Excellent - I'll definitely go along to the Leeds night, though as an "out-of-towner" I'll have to leave before the end to get a train home. Do you know the running order yet? Thanks Stephen -- Read the whole topic here: Haskell Art: http://lurk.org/r/topic/B8fIDfP0bnGaTUJr9TpGW To leave Haskell Art, email haskell-...@group.lurk.org with the following email subject: unsubscribe
Re: [haskell art] haskell dependency management over time
― Attachment links are at the end of this email ― Em 02-07-2014 14:14, Al Matthews escreveu: > Ah .. I see .. nix would obviate much of that work. Thanks for the > reference. > > > On Wed, Jul 2, 2014 at 9:09 AM, Al Matthews wrote: > >> Hi Miguel, >> >> I agree that this sounds right. In practice, what do you imagine that >> implies in terms of system sprawl? I mean, I would imagine one is at least >> tripling or quadrupling the Haskell footprint. Yes, that and cpu cycles wasted in compiling is the price to pay for no cabal hell. Storage is cheap these days, though... >> >> I'm afraid this is probably edging up to a general question about art >> preservation maintenance. I don't mean to go off-topic. >> >> But for instance, supposing one feels obligated to stash the OS as well -- >> say one works in a Linux that has a rolling release schedule -- then >> infrastructure grows in turn. >> >> At such point, I suppose one could archive snapshots of systems with >> little Haskell environments per-piece. One VM could archive a number of >> pieces if each were of a modest size. nix would make this quite easy probably, since it makes it quite easy to replicate a whole system configuration. Also, within just one system you can have a haskell setup per project completelly separate. There are some caveats. I did have issues when using cabal with nix, it seems cabal cannot find the libraries correctly in some situations, which means you should just use ghc instead (either directly or via nix-build). Also, nix does not solve the problem of cabal hell directly, since it just keeps a fixed seleciton of haskell packages (like stackage) in it's repository, if you can't use the version there either you have to add the versions you need to the repository (through some .nix files) or you have to use cabal sandboxes and let cabal figure it out. best, Miguel Haskell Art now contains the following file http://lurk.org/r/file/7pebO1VXzI5gtxXYQicdDXuBd1E-8G-2thMnfr Name: signature.asc Type: application/pgp-signature Size: 0KB -- Read the whole topic here: Haskell Art: http://lurk.org/r/topic/ynqkDD6Om6CrN0u7VBoJg To leave Haskell Art, email haskell-...@group.lurk.org with the following email subject: unsubscribe
Re: [haskell art] haskell dependency management over time
Ah .. I see .. nix would obviate much of that work. Thanks for the reference. On Wed, Jul 2, 2014 at 9:09 AM, Al Matthews wrote: > Hi Miguel, > > I agree that this sounds right. In practice, what do you imagine that > implies in terms of system sprawl? I mean, I would imagine one is at least > tripling or quadrupling the Haskell footprint. > > I'm afraid this is probably edging up to a general question about art > preservation maintenance. I don't mean to go off-topic. > > But for instance, supposing one feels obligated to stash the OS as well -- > say one works in a Linux that has a rolling release schedule -- then > infrastructure grows in turn. > > At such point, I suppose one could archive snapshots of systems with > little Haskell environments per-piece. One VM could archive a number of > pieces if each were of a modest size. > > Al > > > On Wed, Jul 2, 2014 at 5:54 AM, Miguel Negrão < > miguel.negrao-li...@friendlyvirus.org> wrote: > >> ― Attachment links are at the end of this email ― >> >> Em 01-07-2014 16:17, Al Matthews escreveu: >> > Hello .. I find Haskell package-management to be a bit of a dark art. >> > >> > In particular, what I find, is that it is easy to break things on which >> I >> > rely. >> > >> > This is compounded no doubt by my use of several development platforms. >> > >> > Still, I wonder if anyone has recommendations on using hsenv, or capri, >> or >> > cabal-dev, or similar. >> > >> > One goal I think, could be to archive a minimal working environment for >> any >> > given major piece. But I don't know if this is a heavy-handed approach, >> and >> > as such, I ask in particular for your experience with maintaining >> Haskell >> > code and systems over time. >> > >> > Thanks, >> > >> > Al >> > >> >> Hi Al, >> >> I would recommend installing only the bare minimum of packages system >> wide (global and for your user), for instance just the haskell platform, >> and install everything else via cabal sandboxes. This way it will be >> unlikelly that you get into trouble again. >> >> Another option is using the nix package manager which can sandbox the >> whole haskell infrastructure, including multiple version of ghc, etc. >> >> best, >> -- >> Miguel Negrão >> http://www.friendlyvirus.org/miguelnegrao >> Haskell Art now contains the following file >> >> http://lurk.org/r/file/hbDVNn6p5ECCYUKozgqyIB63Qij-8G-2thFMqY >> Name: signature.asc >> Type: application/pgp-signature >> Size: 0KB >> >> >> -- >> >> Read the whole topic here: Haskell Art: >> http://lurk.org/r/topic/18U8WkSuHQFTYw24Vd1QVR >> >> To leave Haskell Art, email haskell-...@group.lurk.org with the >> following email subject: unsubscribe >> > > -- Read the whole topic here: Haskell Art: http://lurk.org/r/topic/3rltor0LyCiOnHBkQgOyof To leave Haskell Art, email haskell-...@group.lurk.org with the following email subject: unsubscribe
Re: [haskell art] haskell dependency management over time
Hi Miguel, I agree that this sounds right. In practice, what do you imagine that implies in terms of system sprawl? I mean, I would imagine one is at least tripling or quadrupling the Haskell footprint. I'm afraid this is probably edging up to a general question about art preservation maintenance. I don't mean to go off-topic. But for instance, supposing one feels obligated to stash the OS as well -- say one works in a Linux that has a rolling release schedule -- then infrastructure grows in turn. At such point, I suppose one could archive snapshots of systems with little Haskell environments per-piece. One VM could archive a number of pieces if each were of a modest size. Al On Wed, Jul 2, 2014 at 5:54 AM, Miguel Negrão < miguel.negrao-li...@friendlyvirus.org> wrote: > ― Attachment links are at the end of this email ― > > Em 01-07-2014 16:17, Al Matthews escreveu: > > Hello .. I find Haskell package-management to be a bit of a dark art. > > > > In particular, what I find, is that it is easy to break things on which I > > rely. > > > > This is compounded no doubt by my use of several development platforms. > > > > Still, I wonder if anyone has recommendations on using hsenv, or capri, > or > > cabal-dev, or similar. > > > > One goal I think, could be to archive a minimal working environment for > any > > given major piece. But I don't know if this is a heavy-handed approach, > and > > as such, I ask in particular for your experience with maintaining Haskell > > code and systems over time. > > > > Thanks, > > > > Al > > > > Hi Al, > > I would recommend installing only the bare minimum of packages system > wide (global and for your user), for instance just the haskell platform, > and install everything else via cabal sandboxes. This way it will be > unlikelly that you get into trouble again. > > Another option is using the nix package manager which can sandbox the > whole haskell infrastructure, including multiple version of ghc, etc. > > best, > -- > Miguel Negrão > http://www.friendlyvirus.org/miguelnegrao > Haskell Art now contains the following file > > http://lurk.org/r/file/hbDVNn6p5ECCYUKozgqyIB63Qij-8G-2thFMqY > Name: signature.asc > Type: application/pgp-signature > Size: 0KB > > > -- > > Read the whole topic here: Haskell Art: > http://lurk.org/r/topic/18U8WkSuHQFTYw24Vd1QVR > > To leave Haskell Art, email haskell-...@group.lurk.org with the following > email subject: unsubscribe > -- Read the whole topic here: Haskell Art: http://lurk.org/r/topic/6eW5THmbuNnfdSCNyK3c3u To leave Haskell Art, email haskell-...@group.lurk.org with the following email subject: unsubscribe
Re: [haskell art] haskell dependency management over time
― Attachment links are at the end of this email ― Em 01-07-2014 16:17, Al Matthews escreveu: > Hello .. I find Haskell package-management to be a bit of a dark art. > > In particular, what I find, is that it is easy to break things on which I > rely. > > This is compounded no doubt by my use of several development platforms. > > Still, I wonder if anyone has recommendations on using hsenv, or capri, or > cabal-dev, or similar. > > One goal I think, could be to archive a minimal working environment for any > given major piece. But I don't know if this is a heavy-handed approach, and > as such, I ask in particular for your experience with maintaining Haskell > code and systems over time. > > Thanks, > > Al > Hi Al, I would recommend installing only the bare minimum of packages system wide (global and for your user), for instance just the haskell platform, and install everything else via cabal sandboxes. This way it will be unlikelly that you get into trouble again. Another option is using the nix package manager which can sandbox the whole haskell infrastructure, including multiple version of ghc, etc. best, -- Miguel Negrão http://www.friendlyvirus.org/miguelnegrao Haskell Art now contains the following file http://lurk.org/r/file/hbDVNn6p5ECCYUKozgqyIB63Qij-8G-2thFMqY Name: signature.asc Type: application/pgp-signature Size: 0KB -- Read the whole topic here: Haskell Art: http://lurk.org/r/topic/18U8WkSuHQFTYw24Vd1QVR To leave Haskell Art, email haskell-...@group.lurk.org with the following email subject: unsubscribe
