Re: Providing a smooth default user experience

2012-11-29 Thread Johan Tibell
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

Re: Custom preprocessor with custom file includes

2012-11-29 Thread Jeroen Bransen
Hi all, So, any feedback for this? I still think it is a good idea to move the filetime change check for a preprocessed file from preprocessFile to mkSimplePreProcessor (both in Distribution.Simple.PreProcess). This gives preprocessors the flexibility to define their own dependency tracking, an

Re: Providing a smooth default user experience

2012-11-29 Thread Simon Hengel
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

Re: Providing a smooth default user experience

2012-11-29 Thread Simon Hengel
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

Re: Providing a smooth default user experience

2012-11-29 Thread Johan Tibell
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

Re: Providing a smooth default user experience

2012-11-29 Thread Mikhail Glushenkov
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

Re: Providing a smooth default user experience

2012-11-29 Thread Simon Hengel
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

patch applied (hackage-server): "Fix import for build reports"

2012-11-29 Thread devnull
Thu Nov 29 11:16:07 GMT 2012 Edsko de Vries * Fix import for build reports Ignore-this: c29ac5975354c117184b101e848272d4 Next up: try to do this in a pure fashion M ./Distribution/Server/Features/BuildReports/Backup.hs -2 +2 ___ cabal-de

patch applied (hackage-server): "Fix comparison on tarballs"

2012-11-29 Thread devnull
Thu Nov 29 10:36:19 GMT 2012 Edsko de Vries * Fix comparison on tarballs Ignore-this: 648378d5c1cdccfb8db791fe524f64ce If the tarballs didn't contain the exact same entries, in the exact same order, then `equalTarBall` would report lots of superfluous errors due to a call to `mergeB