Skip to content

unixODBCDrivers: fix broken module invocation #14598

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

Profpatsch
Copy link
Member

environment.unixODBCDrivers was broken, because the type was package,
but the drivers were attrsets that looked like this:

{ ini = "…"; deriv = <derivation>; }

Keep the module type, but move the .inis into passthru.

Remove psqlng, which has been broken since 2008 and was
never finished.

unixODBCDrivers.mysql is broken.

Tested by inserting all available packages in unixODBCDrivers and
rebuilding.

Verified

This commit was signed with the committer’s verified signature.
vdemeester Vincent Demeester
environment.unixODBCDrivers was broken, because the type was `package`,
but the drivers were attrsets that looked like this:
    { ini = "…"; deriv = <derivation>; }

Keep the module type, but move the .inis into `passthru`.

Remove `psqlng`, which has been broken since 2008 and was
never finished.

unixODBCDrivers.mysql is broken.

Tested by inserting all available packages in `unixODBCDrivers` and
rebuilding.
@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @MarcWeber, @vlstill and @bjornfor to be potential reviewers

@bjornfor
Copy link
Contributor

@Profpatsch: Merge conflicts. (I think @abbradar has pushed some improvements to unixODBCDrivers in the meantime.)

@Profpatsch
Copy link
Member Author

Well, it’s been more than a month.

@abbradar
Copy link
Member

abbradar commented May 21, 2016

@Profpatsch I haven't known about your work, sorry. I, too, moved INI attributes to passthru and removed several broken drivers. However, not all drivers do work now -- I think I haven't managed to build MySQL nor MariaDB drivers. What additional changes have you done? I'm willing to help rebasing your improvements atop current master.

EDIT: I have also removed additional tweaks from INI files. My reasoning has been that tweaks should be specified case-by-case and we should stick to defaults. However, if those tweaks are actually considered de facto defaults we can return them -- I'm not knowledgeable enough about ODBC.

@bjornfor
Copy link
Contributor

Reminds me, I have a couple of old branches that attempted to fix MySQL. Never got it to work though. (Why do upstreams make it so difficult to build their software?)

@abbradar
Copy link
Member

I stopped somewhere when after patching CMake to search for MySQL modules properly I got some compilation error.

This all is child's play however compared to Telegram Desktop's building system... but this is offtopic, I just haven't healed mental damage fully.

@bjornfor
Copy link
Contributor

@abbradar: OT: Right, I remember you wrote a bit about that in the PR. Sounded horrible! I hope you eventually heal.

@Mic92
Copy link
Member

Mic92 commented Oct 1, 2016

is this still relevant?

@Profpatsch
Copy link
Member Author

Yes, probably. I will probably have the chance to test it in a few weeks.

@0xABAB
Copy link
Contributor

0xABAB commented Jul 9, 2017

@Profpatsch Please write an issue for this and close this PR if you cannot implement this.

@Profpatsch
Copy link
Member Author

Please write an issue for this and close this PR if you cannot implement this.

That’s some strange wording because there is already an issue (this one) and I am positively able to implement it (as this issue shows).

I will close it, though, because it hasn’t been relevant to me in ages.

@Profpatsch Profpatsch closed this Jul 9, 2017
@0xABAB
Copy link
Contributor

0xABAB commented Jul 9, 2017

@Profpatsch A PR is not an issue. A PR is a possible solution to an issue.

@0xABAB
Copy link
Contributor

0xABAB commented Jul 9, 2017

@Profpatsch If you don't have the interest to fix this, it still means you cannot implement it (due to lack of interest). Whether or not you could implement this given a billion dollars as motivation for example, is not what was under discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants