Needs work
Project:
RDF Extensions
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Apr 2011 at 15:08 UTC
Updated:
25 Feb 2012 at 23:08 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
milesw commentedThis is due to the awkward way the ARC2 location is set, which I believe was carried over from the D6 RDF module. If libraries.module is enabled, RDFx will assume that ARC2 is installed there.
From the first lines in rdfx.module:
We can definitely improve this.
Comment #2
Anonymous (not verified) commentedWould it make sense to have a dependency on libraries? I say this because the way that SPARQL was rewritten, it requires ARC2 as well. Since these modules will often be used on the same site, it seems to make sense to use libraries to manage them.
Views Slideshow has a dependency on libraries, I'm guessing a lot of other modules will too.
Comment #3
milesw commentedI think we should strongly encourage the use of Libraries, but not make it a dependency. Maybe the README and project page should include something about it?
In the issue #1136944: ARC2 is a dependency, but not handled as such scor indicates that SPARQL should be dependent on RDFx. Anything that depends on RDFx will have access to the full set of ARC2 features (assuming ARC is installed properly). Are there other D7 modules using ARC that don't depend on RDFx?
Also, the original issue here may end up fixed by #1124580: Add extra measures to prevent errors when ARC library cannot be found.
Comment #4
scor commentedComment #5
Anonymous (not verified) commentedDiscussing this with scor right now. I checked and it looks like about 50 modules currently have dependencies on libraries.
Comment #6
scor commentedFor those new to this issue, what needs to happen here is to remove any trace of vendor/arc and download the ARC2 lib to the libraries location. All the existing libraries code is good, it's just a matter of removing the conditions and using it all the time.
Comment #7
stefan freudenberg commentedHi. Here's a patch theat addresses the issue and also takes into account people installing ARC2 in the standard php library include path.
Comment #8
scor commentedI'm not sure you want .= in the last line, but rather =?
@Stefan: what do you suggest instead of making libraries a dependency and avoiding the double location confusion then?
Comment #9
stefan freudenberg commented@scor: I the last line you quoted above I want to add all the possible locations to the include path, so it is ".=". This makes it possible to put the library in either location. You can also have the library in the standard include path, e.g. /usr/share/php/arc or something like that. In this patch I replace the vendor location with sites/all/libraries.
Comment #10
stefan freudenberg commentedOk. We should not introduce new ways of loading external libraries here. I have added the dependency on libraries and will add patches there if the include_path approach is beneficial in general.