On Fri, Nov 2, 2012 at 8:43 AM, Duncan Coutts
duncan.cou...@googlemail.com 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
Hi Duncan,
I'm trying to finalize the list of things to include in Cabal/cabal-install
1.18, which I hope to push out by the end of this year. What's the current
status of the cabal repl work? Is it close enough to being finished for
someone else to pick up and take the rest of the way?
In my
On Thursday, November 22, 2012, Manuel M T Chakravarty wrote:
Simon Peyton-Jones simo...@microsoft.com javascript:;:
So the invariant I suggest is
* If it'd work in an empty database, it should work in any non-empty one
* Installing X should never break the existing installation of Y
Hi Simon,
On Thu, Nov 29, 2012 at 6:45 AM, Simon Hengel s...@typeful.net 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
On Thu, Nov 29, 2012 at 8:20 AM, Simon Hengel s...@typeful.net 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
On Tue, Dec 4, 2012 at 8:53 AM, Ian Lynagh ig...@earth.li wrote:
Could someone take a look please? Or perhaps the Cabal wiki should be
moved elsewhere (github?) and the trac instance disabled?
The Cabal bug tracker is already on GitHub:
https://github.com/haskell/cabal/issues
Hi all,
I thought I'd give everyone a status update on the sandboxed build support.
Mikhail has been busy at work implementing automatic rebuilding of
local dependencies. Local dependencies let you can build one
unreleased package against another unreleased package, both residing
in e.g. ~/src.
On Fri, Dec 14, 2012 at 3:29 PM, Ben Millwood hask...@benmachine.co.uk wrote:
Do we therefore have no interest in compilers other than GHC? Can we
drop all instances of ifdef __HUGS__ from the code?
I think doing so would require a reasonable amount of work, but would
significantly lower the
On Fri, Dec 14, 2012 at 3:51 PM, Duncan Coutts
duncan.cou...@googlemail.com wrote:
We should distinguish the compilers that can build Cabal, from those
that cabal supports. Cabal supports several compilers that cannot
themselves build Cabal.
I am happy to drop the support for building Cabal
Hi,
Splitting out a library from cabal-install have been a goal for a long
time. I don't know if we want to just expose every module that's there
today or if we'd like to think a bit more about the API first. Duncan,
what do you think?
-- Johan
On Sun, Dec 30, 2012 at 7:09 PM, Mikhail
The test-suite section can mention the modules directly if we accept some
recompilation.
On Monday, December 31, 2012, Mikhail Glushenkov wrote:
Hi,
On Mon, Dec 31, 2012 at 3:56 PM, Johan Tibell
johan.tib...@gmail.comjavascript:;
wrote:
Hi,
Splitting out a library from cabal-install
Cabal hackers,
With 477 open issues, it's hard to use the bug tracker efficiently
e.g. for prioritizing work. Gregory Collins and I have started
cleaning up some dead bugs. We won't get through all of them, so I
encourage other to join in a try to reproduce bugs and add a note to
the bug if it's
On Tue, Mar 19, 2013 at 6:35 AM, Duncan Coutts duncan.cou...@googlemail.com
wrote:
Go for it!
You'll also notice that the code uses different styles in different
places (because of different authors). We've not gone through and tidied
stuff up because we're lazy and because there never
Hi Jason,
On Tue, Mar 19, 2013 at 10:49 AM, Jason Dagit dag...@gmail.com wrote:
There are a few recommendations in that guide that I'm not a fan of. Below
are the main ones.
I'm confident that for each Haskell programmer out there there are a few
recommendations that Haskell programmer is
On Thu, Mar 21, 2013 at 12:48 PM, Ben Millwood hask...@benmachine.co.ukwrote:
I'm in favour of the first style, and if there's no objections, the patch
I'm currently writing will be split into two commits, the first of which
will beautify all the import lists I'm going to touch, and the second
On Fri, Apr 5, 2013 at 10:39 AM, Ben Millwood hask...@benmachine.co.uk wrote:
There's a whole bunch of Hackage stuff that hasn't been moved yet. I'm
expecting Hackage to get its own wiki, since it has its own source
repository, but I don't know what the plan on that front is exactly.
Thanks
Hi all,
Today I merged Mikhail's sandbox UI changes. I believe this is the
biggest hurdle to get the next release out. We have a few remaining
tickets:
https://github.com/haskell/cabal/issues?milestone=20state=open
and then we should be good to go. I will start with #1106. I think we
can punt
Hi all,
The sandbox functionality now works well enough that I think we should
let it out in the wild. I've created a 1.18 release branch at
https://github.com/haskell/cabal/tree/cabal-install-1.18
My intention is to make any necessary bug fixes on that branch before
the release and then
requires
directory
==1.2.*
directory-1.0.1.2 was excluded because directory-1.2.0.1 was selected
instead
directory-1.0.1.2 was excluded because cabal-install-1.18.0 requires
directory
==1.2.*
Roman
* Johan Tibell johan.tib...@gmail.com [2013-08-06 08:37:57+0200]
Hi all
I'd like to get this out before the end of my vacation, so in the next
two weeks. Any objections to go with the current content of the master
branch?
On Tue, Aug 6, 2013 at 3:28 PM, Roman Cheplyaka r...@ro-che.info wrote:
* Mikhail Glushenkov the.dead.shall.r...@gmail.com [2013-08-06
OK. Sounds good to me.
On Fri, Aug 9, 2013 at 11:05 AM, Mikhail Glushenkov
the.dead.shall.r...@gmail.com wrote:
Hi Johan,
On Thu, Aug 8, 2013 at 9:39 PM, Johan Tibell johan.tib...@gmail.com wrote:
I'd like to get this out before the end of my vacation, so in the next
two weeks. Any
What's the status of this?
On Thu, Aug 15, 2013 at 12:31 AM, Mikhail Glushenkov
the.dead.shall.r...@gmail.com wrote:
Hi Johan,
On Tue, Aug 6, 2013 at 8:37 AM, Johan Tibell johan.tib...@gmail.com wrote:
Are there any fixes that absolutely must make it in before a 1.18
release? Remember
compilation patches you're talking about?)
On Tue, Aug 20, 2013 at 6:11 AM, Herbert Valerio Riedel h...@gnu.org wrote:
On 2013-08-20 at 10:26:07 +0200, Mikhail Glushenkov wrote:
On Mon, Aug 19, 2013 at 11:02 PM, Johan Tibell johan.tib...@gmail.com
wrote:
What's the status of this?
'cabal
Johan,
On Mon, Aug 19, 2013 at 11:02 PM, Johan Tibell johan.tib...@gmail.com
wrote:
What's the status of this?
Fixes for the two remaining release blockers:
https://github.com/haskell/cabal/pull/1430
https://github.com/haskell/cabal/pull/1429
I also wrote a changelog:
https://github.com
Hi Luite,
First let me say I'm excited about GHCJS and like for us to support it in Cabal.
As for the actual changes:
(1) feels like an implementation detail of GHCJS that has been
promoted into something everyone will have to deal with. I would like
us to give this design some more thought
I still think we shouldn't change the CompilerId type. You gave this
motivation for changing it in another thread:
It's not so much an implementation detail of GHCJS itself, but more a side
effect of many people using impl(ghc) flags in their packages to check
whether the compiler supports
a pull req. For other projects (not on
hackage), I think that with some comments/Haddock the CompilerId type they
can be quickly guided towards the right change (usually ignoring the field
or adding Nothing)
luite
On Mon, Aug 26, 2013 at 3:39 PM, Johan Tibell johan.tib...@gmail.com
wrote
Hi all,
We're close to a new release of Cabal/cabal-install and I'd appreciate some
help in testing the new release. To install the release candidate, simply
run:
cabal install http://johantibell.com/files/Cabal-1.18.0.tar.gz
http://johantibell.com/files/cabal-install-1.18.0.tar.gz
Please try
830b16a5acffb5038f7af978f638c93ef3e184fd on master.
On Wed, Aug 28, 2013 at 5:45 AM, Roman Cheplyaka r...@ro-che.info wrote:
Hi,
What does it correspond to in git? Is it the cabal-install-1.18 branch,
or master, or something else?
Roman
* Johan Tibell johan.tib...@gmail.com [2013-08-26
Hi,
I've prepared another RC, including some fixes. This one is based
on 9f374ab45e62924506b992db9157c970c7259a03 on the master branch. If we
don't see any problems with this RC the next few days, I'll release it as
1.18.
Again, to install the RC just run:
cabal install
I've been running a Jenkins build bot for cabal for quite a while:
http://ci.johantibell.com/job/cabal/
It's not as good as it could be, because the Cabal test suite isn't in the
best shape. In particular the InternalLibrary tests are failing at the
moment and I think it's because the tests
Hi all,
With 1.18 out the door it's time to look towards the future. Here are
the major themes I'd like to see us work on next:
## Faster builds
There are several interesting things we could do and are doing here.
* Avoid relinking if possible. This reduces incremental build times
(i.e. when
I pasted your report into the bug tracker:
https://github.com/haskell/cabal/issues/1478
I don't know if you're on GitHub or not so I could link the report to your user.
On Thu, Sep 5, 2013 at 8:16 AM, Rogan Creswick cresw...@gmail.com wrote:
I ran into another oddity due to old build artifacts
On Thu, Sep 5, 2013 at 12:06 PM, Iustin Pop iu...@k1024.org wrote:
On Wed, Sep 04, 2013 at 09:14:03PM -0700, Johan Tibell wrote:
## Do the right thing automatically
The focus here should be on avoiding manual steps the cabal could do
for the user.
* Automatically install dependencies when
Of
| Johan Tibell
| Sent: 05 September 2013 05:14
| To: cabal-devel@haskell.org
| Subject: What's next?
|
| Hi all,
|
| With 1.18 out the door it's time to look towards the future. Here are
| the major themes I'd like to see us work on next:
|
| ## Faster builds
|
| There are several
You raise a good point that sandboxing only addresses the issue of
conflicts between two projects (that want to use different
dependencies), but not the issue of actually using two different
versions of a package (at different versions) in a single project*.
The latter is valuable but also a bit
Hideyuki Tanaka was missing from the list of contributors (his patch was
applied through me). His contribution made 'cabal update' faster!
On Wed, Sep 4, 2013 at 2:11 PM, Johan Tibell johan.tib...@gmail.com wrote:
Hi all,
On behalf of the cabal maintainers and contributors I'm proud
Hi all,
Who manages www.haskell.org? Where's the machine? How can I get an SSH
account so I can upload the Cabal user guide for the Cabal version I
just released?
-- Johan
___
cabal-devel mailing list
cabal-devel@haskell.org
The sources (.md) files are already on GitHub. Are there other sources as well?
On Fri, Sep 6, 2013 at 9:32 PM, Mikhail Glushenkov
the.dead.shall.r...@gmail.com wrote:
Hi Johan,
On Sat, Sep 7, 2013 at 12:09 AM, Johan Tibell johan.tib...@gmail.com wrote:
Hi all,
Who manages www.haskell.org
Hi all,
While the sources of some of the documentation is already in git, much
of the website (http://www.haskell.org/cabal/) isn't. I suggest we
check it in under a website/ directory, next to the Cabal and
cabal-install directories.
-- Johan
___
Next Monday is the feature freeze for GHC 7.8. That means that we should
try to fix any critical bugs in the Cabal library before that so we ship a
solid version of Cabal together with GHC. As of today there's only one
unreleased commit to Cabal-1.18.0.
On Tue, Oct 8, 2013 at 10:40 AM, Adam Foltzer acfolt...@gmail.com wrote:
Would this cause `cabal build` to fetch dependencies if some are missing
locally? We'd want to see a similar way to disable that behavior for
security-sensitive environments as well. Reproducibility and isolation are
our
On Sun, Oct 27, 2013 at 4:58 PM, Mikhail Glushenkov
the.dead.shall.r...@gmail.com wrote:
Hi,
On Sun, Oct 27, 2013 at 9:50 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
I am trying to compile cabal-install-1.18.0.2 on GHC-6.12.1. It aborts
with:
...
[12 of 73]
under
way at https://github.com/haskell/cabal/pull/1519. That thread could
probably need some input for people other than me.
-- Johan
On Thu, Sep 5, 2013 at 6:14 AM, Johan Tibell johan.tib...@gmail.com wrote:
Hi all,
With 1.18 out the door it's time to look towards the future. Here are
the major
Hi,
Cabal development is continuing at a furious pace. There are lots of great
things in master that I'd like to get out to users, such as
* relinking avoidance
* build -j
* ability to specify exact deps on the command line
* haskell-suite compiler support
* bug fixes
Here's an approximate
[mailto:cabal-devel-boun...@haskell.org] *On Behalf
Of *Johan Tibell
*Sent:* 27 November 2013 21:01
*To:* cabal-devel@haskell.org
*Subject:* Should we aim for a new release in late January?
Hi,
Cabal development is continuing at a furious pace. There are lots of great
things in master
the other great stuff
the Cabal team are doing.)
Simon
*From:* Johan Tibell [mailto:johan.tib...@gmail.com]
*Sent:* 28 November 2013 12:07
*To:* Simon Peyton-Jones
*Cc:* cabal-devel@haskell.org
*Subject:* Re: Should we aim for a new release in late January?
Hi Simon,
I don't think it's
It would be nice if we could make an effort to either shepherd these
through or close them.
Any major outstanding bugs that need to be fixed before the release?
-- Johan
On Wed, Nov 27, 2013 at 10:01 PM, Johan Tibell johan.tib...@gmail.comwrote:
Hi,
Cabal development is continuing
Hi David,
Great to here that you're going to hack on cabal. We need all the
contributors we can get!
The general roadmap for 1.20 is here:
http://www.haskell.org/pipermail/cabal-devel/2013-September/009533.html
The Do the right thing automatically section is probably the most newbie
friendly.
On Mon, Jan 6, 2014 at 3:33 PM, Brandon Allbery allber...@gmail.com wrote:
On Mon, Jan 6, 2014 at 5:27 AM, Malcolm Wallace malcolm.wall...@me.comwrote:
I think the fundamental problem is that Haddock is now built on top of
ghc. So if a package cannot be built by ghc (for whatever reason,
through working on #674 before I found #1550 and saw that
work is being done there.
There are a few bugs / enhancements I'm keen to have a go at, but I'll
take that part of the discussion to github.
Cheers,
Dave
On Mon, Jan 6, 2014 at 10:53 PM, Johan Tibell johan.tib...@gmail.comwrote:
Hi
What's you username?
On Sun, Feb 23, 2014 at 2:51 PM, Dominic Steinitz domi...@steinitz.orgwrote:
I am trying to upload a new version of a package but I get a page saying
no authorisation provided (the url is
http://hackage.haskell.org/packages/candidates/) and I could find no way
of
You're on the uploader list at least. What does cabal upload -v3 say?
On Sun, Feb 23, 2014 at 2:59 PM, Dominic Steinitz domi...@steinitz.orgwrote:
DominicSteinitz
Dominic Steinitz
domi...@steinitz.org
http://idontgetoutmuch.wordpress.com
On 23 Feb 2014, at 13:58, Johan Tibell johan.tib
you get if you use the web
interface. So my problem is solved. I guess most people use the CLI?
Thanks for your help
Dominic Steinitz
domi...@steinitz.org
http://idontgetoutmuch.wordpress.com
On 23 Feb 2014, at 14:04, Johan Tibell johan.tib...@gmail.com wrote:
You're on the uploader list
Yes. I also prefer the latter, it's more diff friendly and has more
consistent indentation. We should pick and indentation amount (2 or 4) and
stick with it. I vote for 2, just because that's what I use. :)
If we could encode a style guide in a formatter, it would be much easier
for us to do
On Wed, Feb 26, 2014 at 3:51 PM, Tillmann Rendel
ren...@informatik.uni-marburg.de wrote:
1. change `cabal init` to use the pretty printer.
2. expose the pretty printer at the command line.
Agreed on both points. We should add (2) as `cabal format` (similar to
go-fmt) or something like
On Fri, Feb 28, 2014 at 9:04 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
Following Mikhail Glushenkov's advice I have prepared a separate tool that
checks PVP compliance of imports as proposed in:
https://github.com/haskell/cabal/issues/1703
I added some feedback in this
Hi all,
I've uploaded release candidates for Cabal-1.18.1.3 (to be shipped with GHC
7.8) and cabal-install-1.18.0.3.
You can install the RCs like so:
cabal install http://johantibell.com/files/Cabal-1.18.1.3-rc.tar.gz
http://johantibell.com/files/cabal-install-1.18.0.3-rc.tar.gz
It's
On Sat, Mar 1, 2014 at 4:12 PM, Daniel Trstenjak daniel.trsten...@gmail.com
wrote:
On Sat, Mar 01, 2014 at 01:58:14PM +0100, Daniel Trstenjak wrote:
is there a reason why the function 'fieldGet' of 'FieldDescr' in
'Distribution.ParseUtils' formats only the contents of the field
and not
Hi,
I've just made a release of Cabal/cabal-install, for the benefit of GHC 7.8.
People have in the past expressed a desire for having prebuilt
binaries of cabal-install. I'm happy to upload such binaries if people
send them to me. Please specify for which arch/OS the binary is built.
-- Johan
Hi,
With the 1.18 releases for GHC 7.8 out of the way, I'm going to retire
the 1.18 branch* so please don't push any more commits to it.
* Except if there are any late minute fixes *required* for GHC 7.8 to work well.
-- Johan
___
cabal-devel mailing
Hi,
I'd like to get 1.20 out by the end of the month. There's enough
interesting stuff in there to be worth making a release.
Here are the current open issues for the 1.20 milestone:
https://github.com/haskell/cabal/issues?milestone=21
These are mostly feature requests so we could technically
Please do. Gregory Collins and I took a stab at it at some point too, but
there are lots and lots of bugs. Feel free to mark bugs as obsolete and
close them if there haven't been any action in a long time.
On Sat, Mar 15, 2014 at 12:50 AM, Bryan O'Sullivan b...@serpentine.comwrote:
There are
On Wed, Apr 2, 2014 at 12:22 PM, Herbert Valerio Riedel h...@gnu.org wrote:
On 2014-04-01 at 22:43:47 +0200, Nikita Karetnikov wrote:
Turns out cabal-install itself uses HTTP. (Try to grep for hackage in
the source tree.) Is it due to the HTTP library, which doesn't support
HTTPS
On Thu, Apr 3, 2014 at 12:02 AM, Nikita Karetnikov nik...@karetnikov.orgwrote:
The big question we have to answer first is, how do we want to support
SSL?
Do we want to use an existing, well-tested, well scrutinized SSL
implementation and FFI bind to it? If so, which one and why? If not,
Hi!
I looked over and replied to the remaining outstanding pull requests a
couple of days ago. I'm happy to call what's in master now 1.20 (although
I'm also happy if any of the outstanding pull requests make it in.) If
nothing major happens I will make a release on the 15th.
P.S. There are 360
Could you try to `git bisect` it down to the failing commit?
On Wed, Apr 9, 2014 at 11:36 PM, Sergei Trofimovich sly...@gmail.comwrote:
On Wed, 9 Apr 2014 23:03:00 +0200
Johan Tibell johan.tib...@gmail.com wrote:
Hi!
I looked over and replied to the remaining outstanding pull requests
We currently have an OS X Mavericks binary but we also need at least a
Windows binary:
http://www.haskell.org/cabal/download.html
If someone could build me a Windows binary that would be great.
___
cabal-devel mailing list
cabal-devel@haskell.org
Hi all,
I've prepared the 1.20 release candidates. I now need some help testing,
especially on Windows as I don't have a Windows machine.
To install the release candidates simply run:
cabal install http://johantibell.com/files/Cabal-1.20.0-rc.tar.gz
of `map', namely
`(\ u - fromMaybe u (u `relativeTo` baseURI))'
try using the 1.20 branch on GitHub instead, as I had to work around a
missing upper bound on network in the HTTP package. cabal-install only
builds reliably with HTTP-4000.2.5 and higher.
On Tue, Apr 15, 2014 at 10:33 AM, Johan
, Johan Tibell johan.tib...@gmail.comwrote:
If you run into this error:
Network/HTTP/Auth.hs:192:49:
Couldn't match expected type `Maybe URI' with actual type `URI'
In the second argument of `fromMaybe', namely
`(u `relativeTo` baseURI)'
In the expression: fromMaybe u (u
Hi all,
The second, and hopefully last, release candidate for Cabal and
cabal-install 1.20 is ready. If no issues are discovered, I plan to release
this on Sunday, April 20th.
You can help test by installing the release candidate and use it for your
day-to-day work:
cabal install
hyperlink-source: True
and it looks like hyperlink-source isn't quite working! What am i doing
wrong?
On Thu, Apr 17, 2014 at 3:06 AM, Johan Tibell johan.tib...@gmail.comwrote:
Hi all,
The second, and hopefully last, release candidate for Cabal and
cabal-install 1.20 is ready. If no issues
Hi,
As per usual I want to provide executables for download for download on the
cabal homepage, for Windows and OS X. I can build the OS X one myself.
Could someone please send me a 64-bit Windows cabal executable?
-- Johan
___
cabal-devel mailing list
Hi all,
While I'm sure we still have a bugfix release or two to make on the 1.20
branch, I thought it'd be worth looking at what we want to accomplish for
1.22. Here are my thoughts on what we should focus on:
## A dependency solver that always works
As Hackage has grown so have the
git dependencies in there as well, and then
disallow a hackage upload for any cabal file with a non-hackage
dependency
listed. I would be happy to contribute time to both design and
implementation.
Ben
On Thu Apr 24 2014 at 10:53:59, Johan Tibell johan.tib...@gmail.com
wrote:
Hi
Hi,
It's that time again. 1.20.0.1 is out and I want to put a Windows
executable for download on the Hackage website. Could someone provide me
with one?
-- Johan
___
cabal-devel mailing list
cabal-devel@haskell.org
We can also provide a Linux executable, but I don't quite know how portable
an executable would be if I build it on e.g. some specific version of
Ubuntu?
___
cabal-devel mailing list
cabal-devel@haskell.org
are the contributors for this release, ordered by number of commits:
* Mikhail Glushenkov
* Johan Tibell
* Duncan Coutts
* Thomas Tuegel
* Ian D. Bollinger
* Ben Armston
* Niklas Hambüchen
* Daniel Trstenjak
* Tuncer Ayaz
* Herbert Valerio Riedel
* Tillmann Rendel
* Liyang HU
* Dominic Steinitz
* Brent
On Wed, May 7, 2014 at 4:22 AM, Jens Petersen j...@community.haskell.orgwrote:
BTW, the Windows exe I sent you was 32-bit, unlike what it says on the
download page.
BTW I just noticed that http://www.haskell.org/cabal/download.html
now says that ghc-7.8.1 ships with Cabal-1.20.0.0
whereas
On Wed, May 7, 2014 at 9:34 AM, Herbert Valerio Riedel h...@gnu.org wrote:
Btw, if you want 32bit+64bit binaries for Ubuntu 12.04LTS in future, you
can steal them of my PPA as well:
For instance, here's how to extract the Linux executable just by using
'wget', 'ar', and 'tar':
wget
Hi all,
There's some important bug fixes in Cabal-1.20.0.1 and
cabal-install-1.20.0.2 and I'd like to upload some binaries to make it
easier for users to upgrade. Could someone build me a Windows binary? We
could also use Linux binaries, but that's less important.
Please make sure you use the
We need to figure out if nginx or the hackage-server is to blame here.
On Tue, Jun 10, 2014 at 1:34 AM, Gintautas Miliauskas
gintautas.miliaus...@gmail.com wrote:
Hi,
first of all, a shout out to all ZuriHac2014 folks, thanks for the gentle
introduction to the deeper trenches of Haskell
I'm making another cabal-install release from the 1.20 branch to fix some
more solver issues. In particular, I'm releasing this commit
3f777568 Treat all flags of a package as interdependent.
Are there any other bug fixes *already in master* that are safe/useful
enough to include in the next
to be
upgradable again
Note that the commit IDs are different since these are cherry-picked form
master.
On Tue, Jun 24, 2014 at 5:41 PM, Bardur Arantsson s...@scientician.net
wrote:
On 2014-06-24 09:38, Johan Tibell wrote:
I'm making another cabal-install release from the 1.20 branch to fix some
I've released cabal-install-1.20.0.3.
On Tue, Jun 24, 2014 at 11:54 PM, Mikhail Glushenkov
the.dead.shall.r...@gmail.com wrote:
Hi,
On 24 June 2014 23:13, Johan Tibell johan.tib...@gmail.com wrote:
Fixed the 1.20 branch. Please revert in master yourself.
Already done
Cabal is allowed to use any version that fullfills the required bounds. It
uses a heuristic the tends to prefer
* installed
* newest
* other
in that order.
If you want to make sure the newest version is used temporarily you can
pass --constraint=foo-1.2.3.4 to cabal install. If you want to
Right
On Wed, Jul 16, 2014 at 9:42 AM, Daniel Trstenjak
daniel.trsten...@gmail.com wrote:
Hi Johan,
On Tue, Jul 15, 2014 at 01:07:17PM +0200, Johan Tibell wrote:
Cabal is allowed to use any version that fullfills the required bounds.
It uses
a heuristic the tends to prefer
Sorry, I read this to quickly as I was in a rush this morning. Sandboxes
consider only the global package DB, not the user package DB.
On Wed, Jul 16, 2014 at 11:59 AM, Roman Cheplyaka r...@ro-che.info wrote:
This doesn't make sense to me. Can you elaborate?
* Johan Tibell johan.tib
It will be less painful to enable profiling by default when someone
finishes the parallel build support for profiling ways. That would
mean that we can build the vanilla and profiling version of a library
at the same time, saving quite a bit of time.
___
Hi,
We don't have any binary builds of 1.20.0.3 so I thought it better to
point to a release where we have such. If someone can provide me with
a windows build (.tar.gz containing exe please, built using latest
Cabal-1.20. Include the arch used in the email.)
I can create a OS X binary and update
Uploaded, thanks!
On Tue, Jul 29, 2014 at 3:13 AM, Mikhail Glushenkov
the.dead.shall.r...@gmail.com wrote:
Hi,
On 24 July 2014 11:41, Johan Tibell johan.tib...@gmail.com wrote:
Hi,
We don't have any binary builds of 1.20.0.3 so I thought it better to
point to a release where we
I'm not again putting out another release, but I'd prefer to make it on top
of 1.20 if possible. Making a 1.22 release takes much more work (RC time,
etc). Which are the patches in question. Can they easily be cherry-picked
onto the 1.20 branch? Are there any risk of breakages?
On Fri, Aug 8,
Edward made some changes so that GHC 7.10 is backwards compatible with
older cabals (older cabals just can't use the new goodies, that's all),
which means that we won't need an earlier release. I'm still aiming for
another major release before 7.10? When's 7.10 scheduled before?
On Fri, Aug 8,
Hi Daniel,
I think we eventually want to move dist/ inside the sandbox and eventually
move the sandbox out of the package directory too. This is too support a
world which is less focused on a single package. See my answer here:
I think I can have a RC out without 2 weeks.
On Tue, Dec 2, 2014 at 8:53 AM, Luite Stegeman stege...@gmail.com wrote:
On Mon, Dec 1, 2014 at 7:40 PM, Bardur Arantsson s...@scientician.net
wrote:
Mostly out of curiousity: is there *any* conceivable chance of getting
the GHCJS bits merged
If someone can figure out what the right fix is and if it happens to be in
Cabal I'd be happy to merge any changes.
On Tue, Dec 2, 2014 at 10:43 PM, Miëtek Bak mie...@bak.io wrote:
On 2014-12-02, at 21:31, Carter Schonwald carter.schonw...@gmail.com
wrote:
whats an example of such a
I've cherry-picked the commit from
https://github.com/haskell/cabal/pull/1990. Are we good to go?
On Wed, Dec 3, 2014 at 9:50 PM, Mikhail Glushenkov
the.dead.shall.r...@gmail.com wrote:
Hi,
On 3 December 2014 at 18:04, Mikhail Glushenkov
the.dead.shall.r...@gmail.com wrote:
We probably
I've merged the patches into the 1.20 branch. Look forward to a patch
release this weekend.
On Thu, Dec 4, 2014 at 1:43 PM, Yitzchak Gale g...@sefer.org wrote:
Bryan O'Sullivan wrote:
It seems that something somewhere in linker-land
changed in GHC 7.8 such that packages that include
C
I've uploaded release candidates for Cabal/cabal-install patch releases on
the 1.18 and 1.20 branches:
https://www.haskell.org/cabal/release/cabal-1.18.1.5/Cabal-1.18.1.5.tar.gz
https://www.haskell.org/cabal/release/cabal-install-1.18.0.6/cabal-install-1.18.0.6.tar.gz
101 - 200 of 235 matches
Mail list logo
