Ticket #22879 (closed defect: fixed)
amarok, amarok-devel should now depend on mysql5 instead of mysql5-devel
| Reported by: | bgrupe@… | Owned by: | illogic-al@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.1 |
| Keywords: | Cc: | ryandesign@… | |
| Port: | amarok, amarok-devel |
Description
After the switch 5.0->5.1 and -devel 5.1->5.4 of MySQL, Amarok can (and should) now depend on mysql5 again, instead of -devel.
Change History
comment:2 Changed 4 years ago by illogic-al@…
- Status changed from new to closed
- Resolution set to fixed
Done in r61537.
comment:3 follow-up: ↓ 4 Changed 4 years ago by snc@…
Was there a reason it shouldn't depend on path:bin/…:mysql ?
comment:4 in reply to: ↑ 3 Changed 4 years ago by ryandesign@…
Replying to snc@…:
Was there a reason it shouldn't depend on path:bin/…:mysql ?
It does depend on path:...:mysql5.
You may want to add a pre-configure check to amarok for the existence of the libmysqld.a, since there is now a variant in mysql5 and mysql5-devel to disable the installation of that component (since that's the component that's preventing us from having a universal build of those ports).
comment:5 Changed 3 years ago by ryandesign@…
- Cc ryandesign@… added
- Port changed from amarok to amarok, amarok-devel
- Summary changed from amarok should now depend on mysql5 instead of mysql5-devel to amarok, amarok-devel should now depend on mysql5 instead of mysql5-devel
Actually, the path to libmysqld.a in the dependency specification was incorrect (as reported on the mailing list) thus negating the purpose of using it, and amarok-devel was not updated either.
I fixed both in r61914 and added the aforementioned pre-configure check.