jay wrote:phoenix: maybe it is a better idea to separate the client from the installer? once you have installed the data files you only need to update the client and don't need to drag again about ~35mb of data for the installer to patch files.
I'm thinking of something like:
app-games/nwn-server - the NWN standalone server for linux
app-games/nwn-client - the linux beta client
app-games/nwn-installer - ravages installer (make nwn-client as dependency)
app-emulation/nwn-winex - the special winex version for the toolset
and maybe
app-games/nwn which will install server, client and the installer or similiar?
what do you think about this?
Hey there.
The ebuild does not use the installer. It uses the linuxclient tar.gz. It's said that the installer has legal issues (because of the windows installer stuff in it). I did not doublecheck it yet, though.
Btw, the policy forbids to have interactive ebuilds, so there's no point in having app-games/nwn-installer.
nwn-client, nwn-server and a meta-package which merges both sounds reasonable though. Thanks for the idea.
nwn-winex should be renamed to winex-nwn to follow my standard wine* naming policy, but it makes more sense then nwwine - i have to admit that.
@grinch:
No fear - nwwine wont kill the other wine's you have lying around. It goes to /usr/lib/nwwine; the launcher is called /usr/bin/nwwine and the regedit tools name is /usr/bin/regedit-nwwine. The configs go to ~/.nwwine.
You can have wine, winex-cvs, nwwine and one of winex or winex-transgaming installed on the same box.
So long,