From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Brian E Gallew <geek+(at)cmu(dot)edu>, Edmund Mergl <E(dot)Mergl(at)bawue(dot)de> |
Cc: | Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Perl library (was Building Postgres) |
Date: | 1999-06-29 15:28:08 |
Message-ID: | 3778E608.D53750FB@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Wouldn't it be better to create a CPAN package and distribute it from
> *there*? I realize that this method has the problem that package
> updates and PostgreSQL updates could become desynchronized, but I
> think this would address the issue adequately.
Well, the problem I'm trying to solve is rpm packaging, which is not
necessarily the same as solving the perl distribution issue.
However...
Would a CPAN package be more amenable to an rpm packaging? That is, if
we had a CPAN distribution (generated locally, of course), could I
plop that into an rpm and have a standard, easy procedure to follow
within the rpm to get the stuff extracted and installed onto a
machine?? I'm blissfully ignorant about CPAN and the packaging
conventions, but would like suggestions.
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1999-06-29 15:52:48 | Re: [HACKERS] Re: Mess |
Previous Message | Brian E Gallew | 1999-06-29 14:52:34 | Re: [HACKERS] acl problem in NetBSD/m68k |