From: Ben G. <bga...@gm...> - 2013-09-18 13:40:42
|
After having demonstrated to myself repeatedly that I'm incapable of operating Darcs correctly, I finally broke down and imported Gtk2hs into Git. My cabal-1.18 branch[1] has the current state of my work to get Gtk2hs building with Cabal 1.18. My intention is to export these patches to apply against my Darcs tree when they are ready. Unfortunately, it's not clear to me how to manage various Cabal changes made in interfaces used by Gtk2HsSetup.hs (in particular programFindLocation) without breaking backwards compatibility. This is particularly problematic as Gtk2HsSetup.hs apparently doesn't have access to the CPP macros typically defined by Cabal. Cheers, - Ben [1] http://github.com/bgamari/gtk2hs/tree/cabal-1.18 |
From: Dominic S. <do...@st...> - 2013-09-20 08:01:34
|
Hi Ben, I have pull request against your 1.18 branch which fixes backwards compatibility (untested on 1.16). Is there any point to exporting to cabal now? Why don't we just stick with git? It's pretty much the de facto standard these days and I used to be a big darcs user. Dominic Steinitz do...@st... http://idontgetoutmuch.wordpress.com On 18 Sep 2013, at 14:40, Ben Gamari <bga...@gm...> wrote: > > After having demonstrated to myself repeatedly that I'm incapable of > operating Darcs correctly, I finally broke down and imported Gtk2hs > into Git. My cabal-1.18 branch[1] has the current state of my work to > get Gtk2hs building with Cabal 1.18. My intention is to export these > patches to apply against my Darcs tree when they are > ready. Unfortunately, it's not clear to me how to manage various Cabal > changes made in interfaces used by Gtk2HsSetup.hs (in particular > programFindLocation) without breaking backwards compatibility. This is > particularly problematic as Gtk2HsSetup.hs apparently doesn't have > access to the CPP macros typically defined by Cabal. > > Cheers, > > - Ben > > > [1] http://github.com/bgamari/gtk2hs/tree/cabal-1.18 > ------------------------------------------------------------------------------ > LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! > 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint > 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes > Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. > http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk_______________________________________________ > Gtk2hs-devel mailing list > Gtk...@li... > https://lists.sourceforge.net/lists/listinfo/gtk2hs-devel |
From: Ben G. <bga...@gm...> - 2013-09-20 12:38:45
|
Dominic Steinitz <do...@st...> writes: > Hi Ben, > > I have pull request against your 1.18 branch which fixes backwards > compatibility (untested on 1.16). > Awesome! That's a pretty clever hack although it still irks me that the interface was changed on the Cabal side in the first place. > Is there any point to exporting to cabal now? Why don't we just stick > with git? It's pretty much the de facto standard these days and I used > to be a big darcs user. > I would certainly prefer to move to git. I've never felt very comfortable with darcs and I believe that many other potential contributors feel similarly. Cheers, - Ben |
From: Ben G. <bga...@gm...> - 2013-09-24 20:04:51
|
Ben Gamari <bga...@gm...> writes: > After having demonstrated to myself repeatedly that I'm incapable of > operating Darcs correctly, I finally broke down and imported Gtk2hs > into Git. My cabal-1.18 branch[1] has the current state of my work to > get Gtk2hs building with Cabal 1.18. My intention is to export these > patches to apply against my Darcs tree when they are > ready. Unfortunately, it's not clear to me how to manage various Cabal > changes made in interfaces used by Gtk2HsSetup.hs (in particular > programFindLocation) without breaking backwards compatibility. This is > particularly problematic as Gtk2HsSetup.hs apparently doesn't have > access to the CPP macros typically defined by Cabal. > > Cheers, > > - Ben > > > [1] http://github.com/bgamari/gtk2hs/tree/cabal-1.18 For the record, this branch should now be in a condition where it will work with Cabals both pre- and post-1.18. Cheers, - Ben |