New Port for dbxml

[remy.apfelbacher@…]

Hi all,

here is a port file for dbxml. Maybe you have some suggestions for improving it. Please let me know.

This port file was tested on OS 10.5.7 with XCode 3.1.2

Best, Ré,y

[remy.apfelbacher@…]

dbxml port file (databases/dbxml/Portfile)

[blb@…]

Is there a reason it depends on the xercesc port but also appears to have its own (built in pre-configure)?

[remy.apfelbacher@…]

Yes. When dbxml is being built it requires the compiled sources of xerces and bdb. That's why these parts are being compiled. The resulting libraries of xerces and bdb are however not installed as there are already portfiles for them. That's why there are the depdencies to them.

Agreed that this is a bit strange but it didn't work any other way. The dbxml documentation refers to this.

[raimue (Rainer Müller)]

I suppose this could leads to problems when xercesc or db46 get updated to a newer version.

[remy.apfelbacher@…]

Something which needs to be checked. What would you propose if so?

[remy.apfelbacher@…]

Digging in the installation guide of dbxml one can see the following:

Each of these packages is freely available and distributed under an Open Source license, although Berkeley DB XML depends on specific versions of each. To build Berkeley DB XML, you will need the following third-party libraries:

Berkeley DB
Berkeley DB is a general purpose database toolkit. This release of Berkeley DB XML includes Berkeley DB 4.6.21 release, and requires the Berkeley DB 4.3.28 release or later.
Xerces
Xerces is the Apache implementation of XML parsing technology and DOM. The build requires a source release of Xerces, not just a binary release. This release of Berkeley DB XML bundles Xerces-C 2.8.0, and requires the Xerces 2.7.0 release or newer.

So updates shouldn't be a problem.Otherwise is there a way to trigger download and compilation process from within the dbxml port file?

[raimue (Rainer Müller)]

You could add db46 and xercesc to distfiles instead of relying on the other ports. Unfortunately we cannot specify dist_subdir per file, which means users would have to download multiple times. The included xercesc seems to be sufficient for other package management systems.

For example, see the ​Arch Linux PKGBUILD.

[remy.apfelbacher@…]

Replying to raimue@…:

You could add db46 and xercesc to distfiles instead of relying on the other ports. Unfortunately we cannot specify dist_subdir per file, which means users would have to download multiple times. The included xercesc seems to be sufficient for other package management systems.

For example, see the ​Arch Linux PKGBUILD.

So you are basically saying to add db46 and xerces2.8 to the "distfiles" section (or which ever versions will be required), right?

The both packages will then be downloaded and compiled twice. Ok, this shouldn't be a big deal e.g. regarding disk usage. But would you also suggest to have them installed in the non standard location/folder, so that they will not get into conflict when the standard "db46" and xercres ports are getting installed regularly?

[remy.apfelbacher@…]

Replying to remy.apfelbacher@…:

Replying to raimue@…:

You could add db46 and xercesc to distfiles instead of relying on the other ports. Unfortunately we cannot specify dist_subdir per file, which means users would have to download multiple times. The included xercesc seems to be sufficient for other package management systems.

For example, see the ​Arch Linux PKGBUILD.

So you are basically saying to add db46 and xerces2.8 to the "distfiles" section (or which ever versions will be required), right?

The both packages will then be downloaded and compiled twice. Ok, this shouldn't be a big deal e.g. regarding disk usage. But would you also suggest to have them installed in the non standard location/folder, so that they will not get into conflict when the standard "db46" and xercres ports are getting installed regularly?

To be a little more precise: the dependent libraries are already included in the src-tgz. So no need to add them to the distfiles.

The dependent libraries could be put in a different folder (e.g. ${prefix}/share/dbxml/{bdb,xerces,xqilla}) rather than the standard folder in order to prevent conflicts?

[remy.apfelbacher@…]

Created a new submission for new version of dbxml. See #24429

Please close this one (#19813)