Re: [HACKERS] removing tsearch2
| От | Mike Blackwell |
|---|---|
| Тема | Re: [HACKERS] removing tsearch2 |
| Дата | |
| Msg-id | CANPAkgu8tUdi-a+TUeA+FW3PS8c9w9X1QjdddGexxOuRhb+sDQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] removing tsearch2 ("David E. Wheeler" <david@justatheory.com>) |
| Список | pgsql-hackers |
There is also a mechanism for the results of the Perl module's "make test" to be reported to a site which aggregates and reports them by Perl version and OS - a sort of distributed build farm. See for example http://matrix.cpantesters.org/?dist=DBD-Pg+3.5.3
__________________________________________________________________________________
Mike Blackwell | Technical Analyst, Distribution Services/Rollout Management | RR Donnelley
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
Mike.Blackwell@rrd.com
http://www.rrdonnelley.com
On Mon, Feb 27, 2017 at 4:02 PM, David E. Wheeler <david@justatheory.com> wrote:
On Feb 27, 2017, at 1:53 PM, Bruce Momjian <bruce@momjian.us> wrote:
> Oh, does CPAN distribute compiled modules or requires users to compile
> them.
Like PGXN, it formally does not care, but its implementation expects source code distributions what will be built and installed by users. Note that the vast majority of those modules, -- even pure Perl modules -- are built with make.
So users typically get their Perl modules in one of these ways:
1. As binaries from their distribution’s package manager. These tend to be updated manually by volunteers and not integrated into CPAN, though there are solutions such as [rpmcpan](https://github.com/iovation/rpmcpan) and [PPM](http://www.activestate. com/activeperl/ppm-perl- modules) which do regular distro package builds.
2. As source code from CPAN, from which they are compiled (when necessary), built, and installed by the user or a build system such as [Homebrew](https://brew.sh).
Best,
David
В списке pgsql-hackers по дате отправления: