[pgrouting-dev] Quick 2.0 Update

[Daniel Kastl]

On Wed, Mar 6, 2013 at 1:45 PM, Daniel Kastl <daniel at georepublic.de> wrote:

>
>
>> I found one thing I don't like about this structure and that is there are
>> more little sql files to deal with, but my hope is that these can all be
>> hidden as part of the CREATE EXTENSION command when I get to that.
>>
>>
> Hi Steve,
>
> CREATE EXTENSION is probably the most user-friendly way, so whether you
> have one SQL file or many, for the user it'S a single command.
>  Another possibility would be to concatenate SQL files as part of the
> build process.
>
> For versions of PostgreSQL where CREATE EXTENSION isn't available yet, a
> template database would be convenient. So a simple script or page in the
> documentation would be enough in that case.
> Thoughts?
>
> How about the library binaries. This would be then also one file per
> algorithm, right?
> Could this be merged into a few as well?
>

Steve, I forgot to mention this:

Should we select a different "default" install directory?
I don't know about Windows, but on Linux, /usr/share/postlbs (or later
/usr/share/pgrouting) was the default destination.
PostGIS puts it'S SQL files into PostgreSQL contrib, and isn't it necessary
to do so if you want to support CREATE EXTENSION?
I'm somehow in favor of PostgreSQL contrib directory.

Daniel




-- 
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de
Web: http://georepublic.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20130306/20f3bd0d/attachment.html>