Peter Eisentraut <pete...@gmx.net> writes:
> That said, I'm obviously outnumbered here. What about the following
> compromise: Use the configure-selected install program inside
> PostgreSQL (which we can test easily), and use install-sh under
> USE_PGXS? Admittedly, the make install time of extensions is probably
> not an issue.
That works for me, since as you say we can easily fix any such bugs
in the core code. The scary thing about this for extension authors
is that they may very well see no bug in their own testing, only to
have their packages fall over in the wild. We shouldn't make each
author who's copied that code rediscover the problem for themselves
that expensively.
> (The affected extensions will still be buggy because users can still
> substitute their own install programs. We're just hiding the issue for
> a while.)
I'm not following this argument. The old makefile coding explicitly set
INSTALL = $(SHELL) $(top_srcdir)/config/install-sh -c
The only way I can see that that would be overridden is an explicit
make INSTALL=/my/random/script install
and surely we cannot guarantee that things don't break when you do
something like that. There are hundreds of ways you can break
the build if you mess with makefile variables. So I'm not prepared
to call it a bug if that doesn't work.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
