Hi all, A couple more things:
Cabal upload is not happy with putting 'build-depends:' in a conditional. I get the following error: "400 Error in upload The dependency 'build-depends: base' does not specify an upper bound on the version number. Each major release of the 'base' package changes the API in various ways and most packages will need some changes to compile with it. The recommended practise is to specify an upper bound on the version of the 'base' package. This ensures your package will continue to build when a new major version of the 'base' package is released. If you are not sure what upper bound to use then use the next major version. For example if you have tested your package with 'base' version 2 and 3 then use 'build-depends: base >= 2 && < 4'." This sounds like a bug to me (I'll ask haskell-cafe separately), but in the meantime, does it make sense to remove support for the 'non-split' base. This means (IIRC) removing support for anything older than ghc-6.10.x. Second thing. Brian, you've done all of the hard work - would you like to make the announcement to the Haskell Universe? (didn't want to imply that I insist on making announcements...) Jeremy 2009/11/12 Jeremy O'Donoghue <jeremy.odonog...@gmail.com>: > Hi all, > > [Eric - note question aimed your way, buried near the bottom] > > 2009/11/10 Brian Lewis <br...@lorf.org>: >> On Tuesday, 10.11.09 at 12:42, Jeremy O'Donoghue wrote: >>> One good option may be to commit the code 'as-is' to enable simple >>> cabal install of wxHaskell, and work on putting back the features we >>> have (temporarily) lost. >> >> If basic functionality is still there, I really favor doing it this way, >> because projects that are hard to install are in the danger zone. > > I agree with Brian and Eric on this and no-one else has commented, so > I have committed the updates to the darcs repo. I've pulled a clean > build and it functions just as expected, but... > >> I'd like to get official wxdirect, wxcore, wx repos in order, maybe >> bumping version numbers as appropriate, and post something to -cafe >> about wxhaskell being truly installable via cabal. I hope this will spur >> interest. I would really like to see this library in good shape. I think >> the most important thing right now is to lower the barrier to using and >> developing on the project. > > While the darcs repo is now in order (with a version bump to 0.12.1.1 > to signify that we are fully cabalized), I'm failing to create a cabal > sdist package for wxcore. > > The error is: > > $ WXWIN=/c/utils/wxWidgets-2.8.10 WXCFG=gcc_dll/mswu runhaskell Setup.hs sdist > Building source dist for wxcore-0.12.1.1... > Setup.hs: Error: Could not find module: Graphics.UI.WXCore.WxcClassInfo with > any suffix: ["gc","chs","hsc","x","y","ly","cpphs","hs","lhs"] > > I remember that we had some trouble with this last time. I thought the > 'extra-tmp-files' stanza indicated that we don't need these files in > the sdist. Eric, you fixed this for me last time. What did you do? > > Happy to upload once I have fixed this - wxdirect is already uploaded, > and I'll do wx in a few moments. Once I've verified the whole chain > using 'cabal install wx' on a clean computer, I'll make the > announcements and update the wiki. It will be a pleasure to simplify > the install instructions :-) > > Regards > Jeremy > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
