wxhaskell-devel

[wxhaskell-devel] cabal install wxcore (and also wxdirect)

[Eric K. <eri...@gm...>]

Hi everybody,

Nice to see wxhaskell making progress!

I was hoping I could jot down some wishlist items for building
wxhaskell...  The big thing on my list is for "cabal install wx" to
"just work".  Right now, you have to

  sudo cabal install wxcore --global
  cabal install wx

which is really quite clunky, especially if you want people to be
able to cabal install stuff which depends on wx

As you know (and the franchise folks may not be aware), our current
cabalisation is a bit of a sham; it just adds some packaging around our
configure script (which is handwritten and not even autoconf-generated!)
and our Makefile.  Would anybody have the time to look into makefile.lib
and see if we can do anything about it?  The ideal, I guess would be to
get rid of our homegrown configure script + makefile combination
altogether.  One thing we could start with is by cabalising wxdirect and
just making wxcore for that.  It seems a little silly having this tool
on hackage that /only/ serves for building wxhaskell (but then maybe one
day it will be useful for working on contribs?)

Another idea to play with is converting our homegrown build system to
use franchise, which may be a better fit for wxhaskell because of
the fanciness of our setup

- franchise:
  http://groups.google.com/group/franchise-haskell/web/home-page

- wxhaskell components:
  http://koweycode.blogspot.com/2008/02/wxhaskell-components-and-news.html

I'm CC'ing the franchise list in case they were interested :-)

Thanks!

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9

Re: [wxhaskell-devel] cabal install wxcore (and also wxdirect)

[shelarcy <she...@gm...>]

Hi,

On Thu, 13 Nov 2008 01:34:38 +0900, Eric Kow <eri...@gm...> wrote:
> I was hoping I could jot down some wishlist items for building
> wxhaskell...  The big thing on my list is for "cabal install wx" to
> "just work".  Right now, you have to
>
>   sudo cabal install wxcore --global
>   cabal install wx
>
> which is really quite clunky, especially if you want people to be
> able to cabal install stuff which depends on wx
>
> As you know (and the franchise folks may not be aware), our current
> cabalisation is a bit of a sham; it just adds some packaging around our
> configure script (which is handwritten and not even autoconf-generated!)
> and our Makefile.  Would anybody have the time to look into makefile.lib
> and see if we can do anything about it?

I added --user option today.

http://www.mail-archive.com/wxh...@li.../msg00337.html

This is not really the solution. Because Cabal and cabal command don't
pass --user option to Distribution.Make's ConfigCmd now.

http://www.haskell.org/ghc/docs/6.10.1/html/libraries/Cabal/Distribution-Make.html

And installation directory isn't $HOME/.cabal now. It causes problem when
use Mac OS X application bundle. See above patch online. Does anybody have
an idea to solve this problem? If we could solve this soonly, we do that
before wxHaskell 0.11 release (We already late some weeks from release date.
GHC 6.10.1 released three weeks ago).

When we solve above two problem, we can use just "cabal install wx"
command to install wxHaskell from Hackage.


Best Regards,

> The ideal, I guess would be to
> get rid of our homegrown configure script + makefile combination
> altogether.  One thing we could start with is by cabalising wxdirect and
> just making wxcore for that.  It seems a little silly having this tool
> on hackage that /only/ serves for building wxhaskell (but then maybe one
> day it will be useful for working on contribs?)

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/

Re: [wxhaskell-devel] cabal install wxcore (and also wxdirect)

[Eric K. <eri...@gm...>]

Hi,

On Fri, Nov 28, 2008 at 12:24:47 +0900, shelarcy wrote:
> I added --user option today.
> 
> http://www.mail-archive.com/wxh...@li.../msg00337.html

I saw that, thanks!

> This is not really the solution. Because Cabal and cabal command don't
> pass --user option to Distribution.Make's ConfigCmd now.
> 
> http://www.haskell.org/ghc/docs/6.10.1/html/libraries/Cabal/Distribution-Make.html

Maybe one hack would be copy the Cabal code to create our own
Distribution.WxhaskellMake, which we can then customise to our needs.

Another solution is to really just find a way to get rid of our
make oriented build method.  If it helps, we could think about
taking over the wxc project, for example and just bless our wrapper
as the new official WxC that we would expect people to install
separately. There would still be the issue of generating the Haskell
code in some of wxcore to deal with :-/

We could also ask Duncan what he thinks; he's quite interested in
wxhaskell's (and gtk2hs's) attempts to cabalise.

> And installation directory isn't $HOME/.cabal now. It causes problem when
> use Mac OS X application bundle. See above patch online. Does anybody have
> an idea to solve this problem? If we could solve this soonly, we do that
> before wxHaskell 0.11 release (We already late some weeks from release date.
> GHC 6.10.1 released three weeks ago).
> 
> When we solve above two problem, we can use just "cabal install wx"
> command to install wxHaskell from Hackage.

Can't wait!

Duncan: I'm CC'ing you.  The wxhaskell team is interested in making
cabal install wxcore "just work".  Right now, you have to "sudo cabal
install wxcore" which is quite horrible :-)

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9

Re: [wxhaskell-devel] cabal install wxcore (and also wxdirect)

[shelarcy <she...@gm...>]

On Fri, 28 Nov 2008 20:52:20 +0900, Eric Kow <eri...@gm...> wrote:
>> And installation directory isn't $HOME/.cabal now. It causes problem when
>> use Mac OS X application bundle. See above patch online. Does anybody have
>> an idea to solve this problem? If we could solve this soonly, we do that
>> before wxHaskell 0.11 release (We already late some weeks from release date.
>> GHC 6.10.1 released three weeks ago).

I find where causes this problem. So, this isn't critical problem for
using cabal command now.

Attached patch is a solution of this problem. I'll push it tomorrow.

Best Regards,

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/

Re: [wxhaskell-devel] cabal install wxcore (and also wxdirect)

[shelarcy <she...@gm...>]

Pushed.

On Fri, 28 Nov 2008 22:47:04 +0900, shelarcy <she...@gm...> wrote:
>>> And installation directory isn't $HOME/.cabal now. It causes problem when
>>> use Mac OS X application bundle. See above patch online. Does anybody have
>>> an idea to solve this problem? If we could solve this soonly, we do that
>>> before wxHaskell 0.11 release (We already late some weeks from release date.
>>> GHC 6.10.1 released three weeks ago).
>
> I find where causes this problem. So, this isn't critical problem for
> using cabal command now.
>
> Attached patch is a solution of this problem. I'll push it tomorrow.

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/

Re: [wxhaskell-devel] cabal install wxcore (and also wxdirect)

[Duncan C. <du...@ha...>]

On Fri, 2008-11-28 at 11:52 +0000, Eric Kow wrote:
> Hi,
> 
> On Fri, Nov 28, 2008 at 12:24:47 +0900, shelarcy wrote:
> > I added --user option today.
> > 
> > http://www.mail-archive.com/wxh...@li.../msg00337.html
> 
> I saw that, thanks!
> 
> > This is not really the solution. Because Cabal and cabal command don't
> > pass --user option to Distribution.Make's ConfigCmd now.
> > 
> > http://www.haskell.org/ghc/docs/6.10.1/html/libraries/Cabal/Distribution-Make.html
> 
> Maybe one hack would be copy the Cabal code to create our own
> Distribution.WxhaskellMake, which we can then customise to our needs.

Is there a cabal ticket filed for this? If so has anyone noted that it's
important for wxhaskell?

I expect passing --user to configure or make isn't the right solution,
but specifying exactly which ghc package db to register into instead
(just like we pass --prefix etc).

Either way it doesn't sound difficult. Patches welcome.

> Another solution is to really just find a way to get rid of our
> make oriented build method.

Or that.

Duncan

Re: [wxhaskell-devel] cabal install wxcore (and also wxdirect)

[shelarcy <she...@gm...>]

Hi, I created ticked for this problem today.

http://hackage.haskell.org/trac/hackage/ticket/431

Best Regards,

On Sat, 29 Nov 2008 00:24:11 +0900, Duncan Coutts <du...@ha...> wrote:
>> > This is not really the solution. Because Cabal and cabal command don't
>> > pass --user option to Distribution.Make's ConfigCmd now.
>> >
>> > http://www.haskell.org/ghc/docs/6.10.1/html/libraries/Cabal/Distribution-Make.html
>>
>> Maybe one hack would be copy the Cabal code to create our own
>> Distribution.WxhaskellMake, which we can then customise to our needs.
>
> Is there a cabal ticket filed for this? If so has anyone noted that it's
> important for wxhaskell?
>
> I expect passing --user to configure or make isn't the right solution,
> but specifying exactly which ghc package db to register into instead
> (just like we pass --prefix etc).
>
> Either way it doesn't sound difficult. Patches welcome.
>
>> Another solution is to really just find a way to get rid of our
>> make oriented build method.
>
> Or that.

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/