| Summary: | ebuild for perl-module DBD::MaxDB | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sven <sven.koehler> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | enhancement | CC: | perl |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
ebuild for DBD::MaxDB 7.5.0.24a
DBD-MaxDB-7.5.00.26.ebuild |
||
|
Description
Sven
2005-02-08 19:56:23 UTC
Created attachment 50797 [details]
ebuild for DBD::MaxDB 7.5.0.24a
First version of ebuild. Works for fine for me.
Created attachment 57166 [details]
DBD-MaxDB-7.5.00.26.ebuild
new version of DBD-MaxDB. this time, it is linked against precompiled SQLDBC
7.6.0.9 which doesn't need lib-compat anymore.
Adding mysql folks since they would have a better say in this. I can say that the ebuild could use some tweaking (src_install block can be dropped; not sure i follow the point of the sed where it is, but probably because i haven't tried to build this; wouldn't export that test db stuff - wouldn't run tests in general). mostly hoping the mysql folks will either waive the baton and say this is ok or not :) while tweaking, you may find out, that several things i did are necessary though don't remeber what could be improved. one problem is, that this ebuild installs libSQLDBC_C.so directly, but without all the nice utilities that come with the SQLDBC-library. These utilities would be needed to setup some user-specific settings like debug-logfiles etc. If DBD::MaxDB goes into portage, i would do it that way: - setup virtual/maxdb-sqldbc - provide a maxdb-sqldbc-bin ebuild that installs pre-compiled SQLDBC-library - provide a maxdb-server ebuild that compiled server and sqldbc from scratch The problem is, that afaik sqldbc cannot be build seperatly. so people would need to compile the whole MaxDB-thing just to get SQLDBC. So having a seperat SQLDBC would be clever. MaxDB was previously SAP-DB, and the only reason that it seems to have ended up with the mysql devs here is that MySQL AB are the present owners of MaxDB. We aren't willing to take on such a large task, as it isn't anything to do with the MySQL database. Sometime in the last year I did put out a request on gentoo-dev for maintainers willing to handle MaxDB, but nothing came of it. Thanks robbat, worth asking :) (removing mysql folks since they aren't as involved as I surmised originally). Unless I can find someone else willing/able to attest to its working function, I can't add this to the tree (since I would become maintainer, and there's no way for me to debug problems with it). Why can't you just install this via g-cpan (either current, or if you wait, the new super sleeked version)? We don't routinely add modules to the tree unless they fill a dep anyway, with a few rare exceptions. (bugzie's acting up on me, let me try that removal again) tossing this into the maintainer-wanted pile so that it isn't lost if someone decides they can pick it up Mass reassign from maintainer-wanted to perl-request Is anyone still interested in this? If yes, please say so here and now! I reported this, but I don't use MaxDB anymore these days. I think, MaxDB is now back in SAP's hands (not MySQL anymore). Last version of DBD::MaxDB on CPAN is from 2006. (In reply to Sven from comment #11) > I reported this, but I don't use MaxDB anymore these days. I think, MaxDB is > now back in SAP's hands (not MySQL anymore). Last version of DBD::MaxDB on > CPAN is from 2006. OK thanks! |
