
It appears that in Cabal-1.1.6, Distribution.Compat.FilePath is hidden (I don't have it installed, just a complaint from a user trying to install Takusen with ghc-6.6). I had a look around and found this message: http://www.haskell.org/pipermail/cabal-devel/2006-September/000165.html which says to me that it ought to be exposed. What's happened here? Has it moved somewhere else, or is it unintentionally hidden? FWIW, I'm using just the splitFileName and joinPaths functions, so if there are equivalents somewhere else that I ought to be using, I'd love to know. Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************

Hi
Why not use my FilePath library,
http://www-users.cs.york.ac.uk/~ndm/projects/libraries.php
Rather than being an internal implementation of detail that got
exposed, this library is nice, works on Windows in all cases, and I
am still pushing for it to be included in base (expect another push in
about a fortnight). It provides both the functions you are asking for,
Thanks
Neil
On 10/24/06, Bayley, Alistair
It appears that in Cabal-1.1.6, Distribution.Compat.FilePath is hidden (I don't have it installed, just a complaint from a user trying to install Takusen with ghc-6.6). I had a look around and found this message:
http://www.haskell.org/pipermail/cabal-devel/2006-September/000165.html
which says to me that it ought to be exposed.
What's happened here? Has it moved somewhere else, or is it unintentionally hidden?
FWIW, I'm using just the splitFileName and joinPaths functions, so if there are equivalents somewhere else that I ought to be using, I'd love to know.
Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ***************************************************************** _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

On Tue, 2006-10-24 at 10:07 +0100, Bayley, Alistair wrote:
It appears that in Cabal-1.1.6, Distribution.Compat.FilePath is hidden (I don't have it installed, just a complaint from a user trying to install Takusen with ghc-6.6). I had a look around and found this message:
http://www.haskell.org/pipermail/cabal-devel/2006-September/000165.html
which says to me that it ought to be exposed.
What's happened here? Has it moved somewhere else, or is it unintentionally hidden?
It was the intention to leave it exposed for the time being. Indeed if you build Cabal with Cabal then it is. However, the ghc build system for packages doesn't currently use Cabal and the .cabal and Makefiles were not kept in sync properly (which was probably my fault) so the result is that whether the module is exposed or not depends on if you use the one built with the ghc build system, or built separately with Cabal. One solution is to recommend to your users that they upgrade to Cabal-1.1.6.1. This will be built using Cabal itself and so it'll be ok. It also fixes a couple minor bugs. Or use the proper FilePath module/package. Really, the only valid excuse for using what ought to be a hidden module is if it's used in a Setup.hs script since they are not allowed to have external package deps. Duncan
participants (3)
-
Bayley, Alistair
-
Duncan Coutts
-
Neil Mitchell