Public bug reported:
This macro wasn't in Zorba 2.0. Therefore, using it in modules means
that those modules require Zorba 2.1 for building, even though they (as
far as I know) don't need it for running.
There will probably be cases in the future where such dependencies are
un-avoidable, but in this case SET_CMAKE_MODULE_PATH is at best a small
convenience, so I don't think it's worth the cost. In fact, I think it's
actually kind of a bad idea, because it enforces a directory naming
convention on module authors.
** Affects: zorba
Importance: Medium
Assignee: Gabriel Petrovay (gabipetrovay)
Status: New
** Changed in: zorba
Importance: Undecided => Medium
** Changed in: zorba
Assignee: (unassigned) => Gabriel Petrovay (gabipetrovay)
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/874676
Title:
Remove SET_CMAKE_MODULE_PATH
Status in Zorba - The XQuery Processor:
New
Bug description:
This macro wasn't in Zorba 2.0. Therefore, using it in modules means
that those modules require Zorba 2.1 for building, even though they
(as far as I know) don't need it for running.
There will probably be cases in the future where such dependencies are
un-avoidable, but in this case SET_CMAKE_MODULE_PATH is at best a
small convenience, so I don't think it's worth the cost. In fact, I
think it's actually kind of a bad idea, because it enforces a
directory naming convention on module authors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zorba/+bug/874676/+subscriptions
--
Mailing list: https://launchpad.net/~zorba-coders
Post to : zorba-coders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zorba-coders
More help : https://help.launchpad.net/ListHelp
