| From: | Markus Wanner <markus(at)bluegap(dot)ch> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org>, Ryan Taylor <rgtaylor1989(at)gmail(dot)com>, pgsql-pkg-debian(at)postgresql(dot)org |
| Subject: | Re: Missing Postgis.control |
| Date: | 2017-06-16 08:46:15 |
| Message-ID: | eb34b0f5-1b73-e8c4-dbac-ef29c8e0c24c@bluegap.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-debian |
On 06/16/2017 10:31 AM, Christoph Berg wrote:
> It doesn't say that it is needed for the initial installation as well.
Correct, that should be included in the (long) description.
> From UX viewpoint, it would be nice if "apt-get install
> postgresql-9.6-postgis-2.3" just worked.
It does. At least as long as you don't disable installation of
recommended packages *and* don't another version of the scripts
installed, already.
Actually, even just installing `postgis` does the trick, then.
> My idea would be:
>
> Package: postgresql-9.6-postgis-2.3
> Depends: postgresql-9.6-postgis-scripts
IIRC that's what we had before, but reverted forth and back to versioned
scripts packages...
> ... users could even install older postgis extensions by using
> the correct CREATE EXTENSION ... VERSION command.
Does that work for older versions when postgis.control is from the most
current one? IIRC that's the only file that really requires the -scripts
packages to conflict.
> Hrm. I'll try discussing that with the colleagues here, maybe they
> have an idea.
Thanks.
Kind Regards
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-06-17 22:24:08 | Re: Missing Postgis.control |
| Previous Message | Christoph Berg | 2017-06-16 08:31:46 | Re: Missing Postgis.control |