First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 33106
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: PgSQL Bugs <pgsql-bugs@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Mathias Hasselmann <mathias.hasselmann@gmx.de>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
libpq++-4.0-r2.ebuild The new .ebuild text/plain Mathias Hasselmann 2003-11-09 15:47 0000 972 bytes Details
libpq++-dirvars.patch The directory-variable patch. patch Mathias Hasselmann 2003-11-09 15:48 0000 1.80 KB Details | Diff
libpq++-4.0-r2.ebuild A new new .ebuild text/plain Mathias Hasselmann 2003-11-09 16:16 0000 906 bytes Details
libpq++-dirvars.patch A new directory-variable-patch patch Mathias Hasselmann 2003-11-09 16:18 0000 1.79 KB Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 33106 depends on: Show dependency tree
Show dependency graph
Bug 33106 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-11-09 15:46 0000
libpq++-4.0-r1.ebuild does odd tricks to fixup installation paths for libpq++.
The attached .ebuild replaces those tricks by a patch, which allows passing
variables to the make program.

The .ebuild also changes the installation locations for libpq++: The current
.ebuild installs in in /usr/include and /usr/lib, whilest all other postgres
files are in /usr/include/postgres and /usr/lib/postgres. From reading libpq++'s
Makefile it appears like the upstream maintainer also suggests
$prefix/include/postgres and $prefix/lib/postgres. This this behavoir also
reduces /usr/include pollution a little bit, I've adopted the second schema.
This step should not cause any problems, since linking with libpq++ also
requires you to like with libpq, which requires /usr/include/postgres to be
added to the include-path and /usr/lib/postgres to the library path anyway.

Well, and finally I've added some statements to install libpq++'s documentation.
Something that's very important for developers using the library. ;-) 

Is there a way to avoid the stuff in examples/ getting compressed?
Should the stuff in examples/ and html/ only be installed, when "docs" is in USE?

Reproducible: Always
Steps to Reproduce:

------- Comment #1 From Mathias Hasselmann 2003-11-09 15:47:12 0000 -------
Created an attachment (id=20486) [edit]
The new .ebuild

------- Comment #2 From Mathias Hasselmann 2003-11-09 15:48:06 0000 -------
Created an attachment (id=20487) [edit]
The directory-variable patch.

------- Comment #3 From Mathias Hasselmann 2003-11-09 15:50:47 0000 -------
Forgot to mention: Also updated HOMEPAGE to point on
http://gborg.postgresql.org/project/libpqpp/projdisplay.php.
Well, and accordingly to that page the package's license is BSD, not LGPL-2.1.

------- Comment #4 From Mathias Hasselmann 2003-11-09 16:16:18 0000 -------
Created an attachment (id=20490) [edit]
A new new .ebuild

D'uh: Just looked at libpq. Installing any crap in /usr/include and /usr/lib
appears to be common sense among the Gentoo core developers. Well, don't
like
it, but I've modified my .ebuild to follow that convention.

------- Comment #5 From Mathias Hasselmann 2003-11-09 16:18:36 0000 -------
Created an attachment (id=20491) [edit]
A new directory-variable-patch

This new patch additionally fixes the way the Makefile creates the libpq++.so
symlink: The Makefile tries to create an absolute symlink, which must produce
nonsense within the sandbox. The patch turns the symlink into a relative
symlink.

------- Comment #6 From Jakub Moc 2005-08-11 05:51:58 0000 -------
The license is still wrong in all dev-cpp/libpqpp ebuilds. Otherwise, I have no
clue if this bug even remotely applies now. So - pgsql herd, please fix the
license at least. 

------- Comment #7 From Tiziano Müller 2006-11-10 18:20:37 0000 -------
Finally fixed. LOL, it took more than 3 years to fix this!!!

First Last Prev Next    No search results available      Search page      Enter new bug