Aidan Van Dyk <ai...@highrise.ca> writes: > I think the general movement is toward *feature* dependancies. So for > intstance, an extension can specify what *feature* it requires, and > difference "versions" of an extension can provide different > "features".
That sounds like what Emacs is doing too. > But checking > http://developer.postgresql.org/pgdocs/postgres/extend-extensions.html, > I don't see any "provides" mechanism. That might be something > actually needed if we are trying to avoid "version" comparisons and > want to be describing actual dependencies... The 'provides' mechanism can be added later I think. It's like saying that in 9.1 an extension 'foo' provides the feature 'foo' and you can't control that, whereas in future version you will be able to control what your extension (and its specific version) provides. Also we will be able to list what the PostgreSQL server provides, maybe, so that compile time options can be depended on by extensions. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
