1 |
On Sunday 21 December 2008 23:45:33 Hilco Wijbenga wrote: |
2 |
> I want to install PostgreSQL but I'm wondering which package to use. |
3 |
> The obvious choice (dev-db/postgresql) installs 8.2.7 but |
4 |
> dev-db/postgresql-server installs 8.3.5. (I see they even use the same |
5 |
> tarball.) Is postgresql-server is the proper way going forward? |
6 |
|
7 |
Yes. |
8 |
|
9 |
postgresql-server is not something new, it's a new way of packaging an |
10 |
existing product. It's like the monolithic/split KDE ebuilds, the new split |
11 |
postgresql packages make the dev's life easier, and make it possible for you |
12 |
to make more modular choices about what you want support for. |
13 |
|
14 |
Plus, the old packages only go as far a version 8.3.1 |
15 |
Only the new packages are supported after that version |
16 |
|
17 |
> What about virtual/postgresql-server? Should I prefer that over |
18 |
> dev-db/postgresql-server? |
19 |
|
20 |
If you emerge the virtual you will get the default method for your platform, |
21 |
whatever that is |
22 |
|
23 |
> Why do we even have a virtual? I thought they were for adding a |
24 |
> service if you don't care which specific package supplies it. |
25 |
|
26 |
You have two packages supplying the same thing - monolithic postgresql and |
27 |
split postgresql. Your system does not care which ebuild you ran to get |
28 |
postgresql, as long as you have one. |
29 |
|
30 |
This is no different to any other virtual, besides the fact that the source |
31 |
tarball is the same one for both. |
32 |
|
33 |
|
34 |
|
35 |
-- |
36 |
alan dot mckinnon at gmail dot com |