Opened 17 years ago
Last modified 17 years ago
#1192 accepted enhancement
Why is psphot dependent on libmysql?
| Reported by: | Michael Wood-Vasey | Owned by: | eugene |
|---|---|---|---|
| Priority: | lowest | Milestone: | |
| Component: | psphot | Version: | current |
| Severity: | minor | Keywords: | |
| Cc: |
Description
I just had a case where there was a problem with the mysql installation on one of the nodes on a cluster and psphot refused to run. Conceptually this seems wrong. psphot shouldn't know anything about libmysql. Why is it required?
I specifically ask because libmsysql is one of the things people have the most trouble compiling and if we'd like the tools in IPP to be as widely used as possible it would be nice to strip mysql and other related functionality that make sense in the standard IPP installation but not just for someone who wants to do photometry.
Change History (2)
comment:1 by , 17 years ago
| Status: | new → accepted |
|---|
comment:2 by , 17 years ago
I think option (1) will be fine for now. For many users who want to install psphot on their individual computers, they will never need MySQL. Because MySQL is one of the dependencies that has historically caused trouble, it would be useful to have that option in the psbuild.
Should psbuild automatically do this if it doesn't find libmysql? Should there be an option to pass? Should we have a 'psbuild -basic' option that doesn't build a lot of things a small-time user will never need (e.g. pstamp, nebulous, etc.)?
the dependency for psphot comes from the dependency down in libpslib. there are two issues here:
1) it is possible to compile the ipp libraries and analysis programs without installing mysql: to do so, it is necessary to supply --with-mysql=no to configure for psLib, and this is not currently enabled in psbuild. adding that to psbuild is a reasonable request.
2) it sounds like the installation built, but somehow a modification to mysql broke a previously working copy of psphot because it could no longer find libmysql. That is a different kind of problem: would it be possible to have psphot, which uses psLib, not load the libmysql code at all, since it does not actually use it (although it has access to psLib APIs which could use mysql). this is much trickier, and probably would require a re-factor of some of the psLib / psModules sections to split off library wrappers into different blocks.
I suspect (2) is not needed to meet the general goal of having more people build and install without problems, and (1) would suffice.