| From: | "Aaron J(dot) Seigo" <aaron(at)gtv(dot)ca> |
|---|---|
| To: | Bruce Bantos <anon(at)mgfairfax(dot)rr(dot)com> |
| Cc: | pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: [GENERAL] RPM vs. tar for 6.5.3 |
| Date: | 1999-11-15 21:58:40 |
| Message-ID: | 99111515000203.15505@stilborne |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
hi...
> It's up to you, really. What I see as a trend for system administrator's
> policies is the eventual migration to "roll-your-own" binaries. For ease
> of use and installation, immediate gratification, etc., go with RPM. For
> configurability of the binary, control of the file-placement schema, and
> security of the source code, "rolling-your-own" is most definitely the way
> to go.
of course, you can make your own RPMs. there are some decent tools out there to
ease this process. so you can roll you own on one system, package it, and
distribute it as RPM across your network...
--
Aaron J. Seigo
Sys Admin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Slavica Stefic | 1999-11-15 23:16:26 | Re: [GENERAL] vacuum analyze works on tables, but not on entire database |
| Previous Message | Aaron J. Seigo | 1999-11-15 21:27:48 | Re: [GENERAL] vacuum analyze works on tables, but not on entire database |