Niklas Broberg writes:

...

I want the executables in /my/chosen/dir/bin but the library to be in /usr/local/lib rather than /my/chosen/dir/lib.

With "ordinary" configure scripts, you can finetune installation using flags like --libdir, --bindir, --includedir etc. This doesn't seem to work with Cabal just yet, but I don't think there are any reasons why it shouldn't be implementable. Feature request? =)

I don't see any problem with this, except that there will be a lot of configure flags if we keep this up. That's typical for configure, though. Also, of course, it adds more complexity to the source.

...

One final thought: why is there no uninstall?

I've requested it too, and the simple answer was because no one's implemented it yet.

Uninstall is also a little funny because in order to use it you have to have the cabal-ized source package around somewhere, and cabal doesn't install it. That said, there's no really deep reason not to have it. I filed wishlist bugs for both of these against the debian package haskell-cabal, which is where i'm keeping but reports. peace, isaac

Dominic Steinitz writes:

On Saturday 16 Apr 2005 8:57 pm, Isaac Jones wrote:

...

...

...

One final thought: why is there no uninstall?

I've requested it too, and the simple answer was because no one's implemented it yet.

Uninstall is also a little funny because in order to use it you have to have the cabal-ized source package around somewhere, and cabal doesn't install it. That said, there's no really deep reason not to have it.

What I meant was cabal taking things out of places it puts them. If I've downloaded a source somewhere I wouldn't expect cabal to remove that.

Right, I understand. What I mean about not installing the source is this: today you download and install the package, and put the source in /usr/local/src or something. Now in 3 weeks you want to install a new version. Well, you might like to run uninstall with the new source, but that's not necessarily going to work, since it doesn't even know how you configured the source package. So the right thing to do is to go into /usr/local/src/pkg and run ./setup uninstall there. So you just have to remember to keep the old source around and go and run uninstall when you want to. But I thought maybe this something that a layered tool should do. Cabal-get (the client-side tool for Hackgae) might download the source into /usr/local, keep track of the source packages it has swallowed, and do the job of uninstalling. So we left it unimplemented until we get a better idea of what cabal-get will look like. peace, isaac