It's rumoured that Justin Clift once said:
> There's more to making PostgreSQL work on Windows than just the "pure
> packaging" issues. We still have to figure out how we're going to
> handle stuff like needed grep, sed, etc just for PostgreSQL to run
> (they're required by initdb).
I thought the idea was initdb would be rewritten in C. We cannot include
grep/sed etc as they're GPL...
> We're also going to need to have a good idea of what other nice
> features could/should be packaged along with it. i.e.:
>
> + a GUI to control some things (installation/deinstallation of the
> PostgreSQL Service, perhaps vacuuming, etc).
Hang on, I heard of a good one the other day... :-)
> + Shortcuts in the Program menu to things (PostgreSQL website(s),
> online documentation, etc)
Those are just decisions to make aren't they? They don't require a Cygwin
proof of concept.
> + Which parts of the installation should be mandatory, and which
> should
> be optional. i.e. Base server files should be mandatory, HTML docs
> should be optional, perhaps include the ODBC driver as optional too.
Likewise, these are decisions to make and then suitable programming of the
installer. Making bits optional should be trivial in any good installer.
Don't get me wrong, I think it's great that someone has finally built a
good Cygwin based package - I just don't think it answers many of the
issues that we will likely encounter.
Regards, Dave.
PS. Is the source on the ftpsite - if not you'll have Jason after you
before long :-)
