Dear Tom,
Agreed. If we are pushing things out, it seems it is our duty to make
it easy for outside things to integrate and build properly.
It does not thereby follow that we should try to merge devel and base
packages (to express it in RPM terms).
They are not necessarily merged, and
Bruce Momjian [EMAIL PROTECTED] writes:
Fabien COELHO wrote:
Well, the point of having an infrastructure if extensions cannot rely it
being there when needed is not clear to me.
Agreed. If we are pushing things out, it seems it is our duty to make
it easy for outside things to integrate and
This is from an extension module author's point of view. My module will
reference these two files only:
Makefile.global
Makefile.shlib
These files possibly include other makefiles.
I'm not the least interested in how these files are organized internally
Sure.
If I have a pg_config
I have a fairly good understanding of how the Makefile.global etc. is
organized. My point is, in order to maintain a good separation of concern, I
should not use this knowledge.
IMHO, there's a need for a well documented module extension build API
accessible from a well known place. This is more
Dear Thomas,
My point is, in order to maintain a good separation of concern, I
should not use this knowledge.
I agree.
IMHO, there's a need for a well documented module extension build API
accessible from a well known place.
Sure.
I'm not really addressing that at the moment, I'm
Fabien COELHO wrote:
Dear Thomas,
My point is, in order to maintain a good separation of concern, I
should not use this knowledge.
I agree.
IMHO, there's a need for a well documented module extension build API
accessible from a well known place.
Sure.
I'm not really
Marc G. Fournier wrote:
On Sat, 15 May 2004, Bruce Momjian wrote:
Fabien COELHO wrote:
Dear hackers,
I wish to submit a small patch so that server includes and
all necessary configuration files could be installed *by default*.
The current status is that server includes files are only
Dear Jan,
Depending on the OS you also need funny things like mkldexport shell
scripts and the like.
Possibly, yes... I don't know. I really need a list, then it is pretty
easy to update all makefiles.
I thought we had a consensus of providing a template build environment
for external
Fabien COELHO wrote:
Any idea? The best I have would be to create a src subdir in the
installation, so that top_builddir could be set to
.../include/postgresql/config and everything would work from that
point of view.
This is from an extension module author's point of view. My module will
Dear Tom,
I wish to submit a small patch so that server includes and
all necessary configuration files could be installed *by default*.
There is a reason why install-all-headers is not the default.
Sure. I hope so!
I'm questionning the pros and cons. I'm arguing that the cons against the
Dear hackers,
Agreed. I would also like to see Makefile.global installed.
pg_config.h has C-level configs, and Makefile.global has the
Makefile-level configs.
There is also config.status which is definitely of interest as it
allows to recreate the build tree, and which is not installed by
I would tend to put everything in include/postgresql/config:
On second thought, I would hesitate with lib/..., as config file are
plateform specific so they cannot be shared with other plateforms,
although it could be the case for include files that they could be shared.
--
Fabien Coelho -
Fabien COELHO [EMAIL PROTECTED] writes:
I wish to submit a small patch so that server includes and
all necessary configuration files could be installed *by default*.
There is a reason why install-all-headers is not the default. It is
that it shouldn't be the default: most people do not need
Fabien COELHO wrote:
Dear hackers,
I wish to submit a small patch so that server includes and
all necessary configuration files could be installed *by default*.
The current status is that server includes files are only installed
if explicitly required (make install-all-headers).
The idea is that
Fabien COELHO wrote:
Dear hackers,
I wish to submit a small patch so that server includes and
all necessary configuration files could be installed *by default*.
The current status is that server includes files are only installed
if explicitly required (make install-all-headers).
The
On Sat, 15 May 2004, Bruce Momjian wrote:
Fabien COELHO wrote:
Dear hackers,
I wish to submit a small patch so that server includes and
all necessary configuration files could be installed *by default*.
The current status is that server includes files are only installed
if
Marc G. Fournier wrote:
As an illustration, the apache software installs by default all
necessary includes and even a special tailored command (apxs) so as
to help extension modules to be compiled, installed and even configured
easilly.
Is there any opposition to this move?
Dear hackers,
I wish to submit a small patch so that server includes and
all necessary configuration files could be installed *by default*.
The current status is that server includes files are only installed
if explicitly required (make install-all-headers).
The idea is that external extension
18 matches
Mail list logo
