Hi Ian, Ross and other interested parties,

I maintain the haskell-filepath Debian source package from which the following packages are build:

haskell-filepath-doc - API documentation of the Haskell FilePath library libghc6-filepath-dev - GHC 6 library for manipulating FilePath's libghc6-filepath-prof - GHC 6 profiling library for manipulating FilePath's libhugs-filepath - Hugs library for manipulating FilePath's

As GHC 6 now ships the Filepath package I am a little bit unsure what to do with my packages. Should I a keep on building the binary packages for GHC 6 or should I replace them by dummy packages which depend on the appropriate binary packages of ghc6?

I am leaning towards the last option which would mean that haskell-filepath would produce the following packages:

haskell-filepath-doc - dummy package depending on ghc6-doc? libghc6-filepath-dev - dummy package depending on ghc6 libghc6-filepath-prof - dummy package depending on ghc6-prof libhugs-filepath - Hugs library for manipulating FilePath's

I am not sure if this is the best option though. Any opinions?

It would be nice if Hugs would also start shipping filepath, so I could drop the libhugs-filepath package as well. Maybe Ross can comment on that?

Greetings Arjan