Hi Duncan,
> Done.
>
> Could you check it works for you now (both with an without a proxy if
> possible).
It works correctly without a proxy, I can't check the other case as I
am not behind a proxy.
Thanks
Neil
___
cabal-devel mailing list
cabal-de
Mon Jun 16 15:38:47 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Default to global installs on Windows
User installs by default elsewhere. Note that this default only
affects new config files. Existing windows users will need to
change their config file or delete it and let it be re-create
#227: cabal-install does consider build-tools as dependencies
-+--
Reporter: guest |Owner: duncan
Type: defect | Status: assigned
Priority: normal |Mile
On Mon, 2008-06-16 at 06:23 +0100, Neil Mitchell wrote:
> Hi
>
> > hive: CURRENT_USER
> > path: Software\Microsoft\Windows\CurrentVersion\Internet Settings
> > key: ProxyServer
> >
> > Can you tell us what is the nearby key that enables/disables use of the
> > proxy?
>
> The DWORD ProxyEna
On Sat, 2008-06-14 at 15:05 +0100, Neil Mitchell wrote:
> Hi,
>
> Using Cabal 1.4 Branch and Cabal-install HEAD:
>
> C:\Neil\uniplate>cabal install --hugs
> Resolving dependencies...
Should work now.
Also "cabal install --hugs whatever" should also work. It assumes that
all deps of "whatever"
On Sun, 2008-06-15 at 21:10 +0100, Neil Mitchell wrote:
> > > I suspect that most people should be doing global installs, and that
> > > local installs should be a secondary option. Not having write access
> >
> > So is that a vote in favour of doing global installs by default on
> > windows o
On Mon, 2008-06-16 at 09:31 -0400, Darrin Thompson wrote:
> Is this buggy behavior?
It's certainly a missing feature.
> I would guess that what alex and happy have in common is that they are
> indirect (second order?) dependencies of the user's specified package.
> Pure speculation on my part.
On Mon, 2008-06-16 at 14:15 +0100, Alistair Bayley wrote:
> I'm trying to build and install Takusen 0.8.2 with a new .cabal and
> Setup, using Cabal-1.4.0.0. The Setup program writes out an updated
> Takusen.buildinfo (below) from the postConf hook. However, the
> library-dirs and include-dirs fie
Mon Jun 16 10:55:11 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Overhaul the bogus dependency resolver so it works again
The bogusResolver is used for compilers like hugs and nhc98 where
we do not know what packages are already installed. We do it by
altering the descriptions of the packa
Mon Jun 16 10:32:53 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Use standard thisPackageVersion rather than inlined definition
M ./Hackage/Install.hs -5 +3
View patch online:
http://darcs.haskell.org/cabal-install/_darcs/patches/20080616173253-adfee-5a41404a583fe4cf3b6c46ee08321b067a2f401
Mon Jun 16 10:12:55 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Move getAvailablePackages into IndexUtils module
M ./Hackage/Fetch.hs -3 +3
M ./Hackage/IndexUtils.hs -2 +12
M ./Hackage/Install.hs -3 +3
M ./Hackage/List.hs -3 +2
View patch online:
http://darcs.haskell.org/cabal
Mon Jun 16 10:03:12 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Try and pick up the http proxy on windows correctly
Takes account of the ProxyEnabled reg key
Allow proxy uris that lack the http:// uri schema.
This should really be moved into the HTTP package.
M ./Hackage/HttpUtils.hs
Mon Jun 16 10:54:46 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Makefile tweak, setup depends on Setup.hs
M ./Makefile -1 +1
View patch online:
http://darcs.haskell.org/cabal/_darcs/patches/20080616175446-adfee-3bd49708601fe35c029c90ceeb57849714bb893e.gz
_
Mon Jun 16 10:15:05 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* construct InstalledPackageInfo from scratch rather than by overriding
It means we catch any fields that get added. As it happens we were
missing a field, though its value is supposed to be just [] which is
the same value as w
#227: cabal-install does consider build-tools as dependencies
-+--
Reporter: guest |Owner: duncan
Type: defect | Status: assigned
Priority: normal |Mile
Is this buggy behavior?
Installing yi...
...
setup: alex version >=2.0.1 && <3 is required but it could not be found.
cabal: Error: some packages failed to install:
yi-0.3 failed during the configure step. The exception was:
exit: ExitFailure 1
$ cabal install alex
Resolving dependencies...
Downl
I'm trying to build and install Takusen 0.8.2 with a new .cabal and
Setup, using Cabal-1.4.0.0. The Setup program writes out an updated
Takusen.buildinfo (below) from the postConf hook. However, the
library-dirs and include-dirs fields are not included in the package
description when installed.
An
Hi
This problem just bit me quite severely. Imagine the scenario:
You install haddock using runhaskell method.
You upgrade haddock, and install it using cabal install.
Both binaries get placed in different places, and depending on your
PATH, you either end up running the old one or the new one.
18 matches
Mail list logo