On Thu, Nov 29, 2012 at 09:01:13AM -0800, Johan Tibell wrote:
> On Thu, Nov 29, 2012 at 8:20 AM, Simon Hengel wrote:
> > On Thu, Nov 29, 2012 at 07:54:34AM -0800, Johan Tibell wrote:
> >> We may very well end up doing this. There's no rush to make it
> >> default. We can make a release with opt-in
On Thu, Nov 29, 2012 at 8:20 AM, Simon Hengel wrote:
> On Thu, Nov 29, 2012 at 07:54:34AM -0800, Johan Tibell wrote:
>> We may very well end up doing this. There's no rush to make it
>> default. We can make a release with opt-in sandboxes and decide three
>> months later if we want to make it the
On Thu, Nov 29, 2012 at 07:54:34AM -0800, Johan Tibell wrote:
> We may very well end up doing this. There's no rush to make it
> default. We can make a release with opt-in sandboxes and decide three
> months later if we want to make it the default.
Nice.
So I guess the idea is that we will have a
On Thu, Nov 29, 2012 at 04:33:05PM +0100, Mikhail Glushenkov wrote:
> > So personally I think it is a better approach to first release the
> > feature, and give people time to try whether there use case are covered.
>
> The idea is to put out a release candidate some time before the final
> releas
Hi Simon,
On Thu, Nov 29, 2012 at 6:45 AM, Simon Hengel wrote:
> Hi Johan,
>
> On Wed, Oct 31, 2012 at 10:22:36AM -0700, Johan Tibell wrote:
>> *Sandboxing should be used by default*
>
> I'm a little bit late on this one. But I'm somewhat skeptical here. As
> I understand it, the sandboxing fea
Hi,
On Thu, Nov 29, 2012 at 3:45 PM, Simon Hengel wrote:
>
> So personally I think it is a better approach to first release the
> feature, and give people time to try whether there use case are covered.
The idea is to put out a release candidate some time before the final
release to give people
Hi Johan,
On Wed, Oct 31, 2012 at 10:22:36AM -0700, Johan Tibell wrote:
> *Sandboxing should be used by default*
I'm a little bit late on this one. But I'm somewhat skeptical here. As
I understand it, the sandboxing feature is not yet released. I think
there is a chance that the first version
Hi Duncan,
> > That is interesting. I'd be interested in how exactly that works. Is
> > there a place where I can read about it? Or if not, can you point me to
> > the related commits?
>
> http://lambdasandwich.blogspot.co.uk/2011/08/ending-gsoc.html
>
> For the changes to ghci see the ghc gi
On Fri, 2012-11-02 at 16:52 +0100, Simon Hengel wrote:
> Duncan,
>
> > > Moreover, it would be awesome if it would regenerate generated source
> > > files on :reload. I'm not sure if this is feasible without changes to
> > > GHCi, but a custom macro, e.g.
> > >
> > > :cabal-reload
> > >
> >
On Fri, Nov 2, 2012 at 8:43 AM, Duncan Coutts
wrote:
>> *cabal build should imply cabal install --only-dependencies
>> *
>> If you're currently working on a package, the right [1] way to build it is
>> as follows:
>>
>> cabal install --only-dependencies
>> cabal build
>
>
> I've been thinking alon
Duncan,
> > Moreover, it would be awesome if it would regenerate generated source
> > files on :reload. I'm not sure if this is feasible without changes to
> > GHCi, but a custom macro, e.g.
> >
> > :cabal-reload
> >
> > could still work.
>
> The GSoC project that started this off did that
On Wed, 2012-10-31 at 10:22 -0700, Johan Tibell wrote:
> Hi all,
>
> Sensible defaults are important to provide a smooth user experience,
> especially for first-time users. There are a few areas where I think cabal
> could improve its default behavior. In particular, here are a couple of
> changes
On Fri, 2012-11-02 at 11:25 +0100, Simon Hengel wrote:
> > Recently, I had to add a MIN_VERSION macro to my code because of the
> > old-time / time change in directory, but couldn't test the library in
> > ghci because the macro was not defined.
> >
> > I discovered that configuring ghci with
> >
Hi,
On Fri, Nov 2, 2012 at 10:48 AM, Björn Peemöller
wrote:
>
> So, if I'm not missing something, it may also be comfortable to add a
>
> cabal ghci
>
> command which tells ghci about cabal's configuration.
There was a "cabal repl" GSoC project last year. The patches haven't
been merged yet, sin
On Fri, Nov 02, 2012 at 11:25:11AM +0100, Simon Hengel wrote:
> > Recently, I had to add a MIN_VERSION macro to my code because of the
> > old-time / time change in directory, but couldn't test the library in
> > ghci because the macro was not defined.
> >
> > I discovered that configuring ghci wi
> Recently, I had to add a MIN_VERSION macro to my code because of the
> old-time / time change in directory, but couldn't test the library in
> ghci because the macro was not defined.
>
> I discovered that configuring ghci with
>
> :set -optP-include -optPdist/build/autogen/cabal_macros.h
>
>
Am 31.10.2012 18:22, schrieb Johan Tibell:
> *We should add a cabal run command*
[snip]
> I think we could improve this use case by introducing a new command,
> cabal run, with the following parameters:
>
> cabal run
>
> which would run
>
> cabal build
> dist/build//
I like this idea, but
On Wed, Oct 31, 2012 at 2:52 PM, Mikhail Glushenkov <
the.dead.shall.r...@gmail.com> wrote:
> On Wed, Oct 31, 2012 at 6:22 PM, Johan Tibell
> wrote:> Since sandboxing is working today (with a few minor tweaks yet to be
> > done) and it can be transparently replaced with a better solution once
>
Hi Johan,
On Wed, Oct 31, 2012 at 6:22 PM, Johan Tibell wrote:
>
> cabal build should imply cabal install --only-dependencies
+1
> The Nix solution is being worked on, as part of GSoC
Is it still being worked on? I thought that the development stalled
after the GSoC period ended.
> Since sand
On 10/31/2012 06:22 PM, Johan Tibell wrote:
> Hi all,
>
> Sensible defaults are important to provide a smooth user experience,
> especially for first-time users. There are a few areas where I think cabal
> could improve its default behavior. In particular, here are a couple of
> changes I would li
Hi all,
Sensible defaults are important to provide a smooth user experience,
especially for first-time users. There are a few areas where I think cabal
could improve its default behavior. In particular, here are a couple of
changes I would like to make:
*cabal build should imply cabal install --o
21 matches
Mail list logo
