Alexander V Vershilov writes:
> Hi, Ben.
>
Hi Alexander!
Thanks for the quick reply.
> It appears that due to the official procedure it takes a large amount of time
> to stabilize platform. We are trying to have latest platform in tree as soon
> as it is available, and stabilization take a larg
I uninstalled, reinstalled , did a cabal install of haddock then ghc-core
and threadscope and saw no errors so I guess we are fine as long as the
next version includes the latest haddock. I notice on the 7.10.2 active
tickets page there is a ticket saying that 7.10.2 needs the latest haddock.
On T
When you did the cabal install of haddock, which haddock did you get? Isn't
2.16.0 the latest? And that should be what is in the Platform.
I guess I should check that the haddock in GHC is actually 2.16.0!
___
Haskell-platform mailing list
Haskell-plat
First and foremost, the packagers for a specific OS distribution should
know best how to match the needs and customs of their constituent
communities. It is not uncommon for packaging to end up shipping something
slightly patched from an official release of a program. And, if it is the
custom of a
Do we have a plan for offering Haskell Platform packaging via MacPorts
or Homebrew? Some users regard these systems as Linux users
regard their distribution's package manager: they should be used if at
all possible. To quote a friend of mine,
> Also, the page should (if it doesn't) address the us
On Tue, Jun 9, 2015 at 11:53 AM, Ben Gamari wrote:
> Do we have a plan for offering Haskell Platform packaging via MacPorts
> or Homebrew? Some users regard these systems as Linux users
> regard their distribution's package manager: they should be used if at
> all possible. To quote a friend of m
Brandon Allbery writes:
> On Tue, Jun 9, 2015 at 11:53 AM, Ben Gamari wrote:
>
>> Do we have a plan for offering Haskell Platform packaging via MacPorts
>> or Homebrew? Some users regard these systems as Linux users
>> regard their distribution's package manager: they should be used if at
>> all
On Tue, Jun 9, 2015 at 8:58 AM, Brandon Allbery wrote:
> Can we have the platform-description-via-cabal-file back? That made it
> easy to use cabal-to-Portfile tooling,
>
? It never left? Only now the haskell-platform.cabal is a built file, not
directly in the repo. See the source tar ball distr
A known pitfall for all is that the OS X native installer package, and
MacPorts build with different install paths, and different library
assumptions. I don't know if Homebrew does it yet differently or is the
same as MacPorts.
This is a constant source of difficultly for users that unwittingly mo
On Tue, Jun 9, 2015 at 11:30 PM, Mark Lentczner
wrote:
> A known pitfall for all is that the OS X native installer package, and
> MacPorts build with different install paths, and different library
> assumptions. I don't know if Homebrew does it yet differently or is the
> same as MacPorts.
>
Tha
10 matches
Mail list logo
