Would you consider joining the gang and Support placing the third-party library in /sites/all/libraries?
I'm using ARC also - for XMP extraction of metadata embedded in images - and would like to avoid doubling up on things like this.
I know path_to_arc can easily be hand-configured, but just thought I'd bring this new and popular approach to your attention to try.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dman’s picture

Issue tags: +Libraries

We have a tag for this!

Dave Reid’s picture

Status: Active » Needs review
FileSize
1.16 KB
911 bytes

Two different patches. One takes an optional approach to Libraries API integration and uses it only if the module is enabled. Other approach creates a dependency on the Libraries API module, which I'd encourage and prefer. I'm actually using the dependency version on my production sites and it's much easier to update the module since I don't have to keep the ARC code inside the module's folder.

dman’s picture

Both fine patches.
I'm wondering if - now that the path is configurable - whether that should be a variable or the resolution should take place closer to the include - rather than a constant.
But I guess because of tight loops and all, it's better out there like that. No practical reason NOT to make it so. I just feel funny when I see constants declared from calculated variables. ... just personal style I guess.

I generally prefer the soft approach, rather than yet another requirement (libraries API is still -dev! ), but maybe making libraries API required will speed its uptake - which I'm behind. libraries API is the new 'token.module' - a shoe-in for core.

So ... generally all good. Patches work. Commit either, I say.
I won't RTBC it yet, as there may be opinion still..

scor’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

ClearXS’s picture

Status: Closed (fixed) » Active

I don't know what is fixed, but apparently not the initial request

Would you consider joining the gang and Support placing the third-party library in /sites/all/libraries?

...as I have the latest dev while as well the project page as the INSTALL.txt say that it has to go into a module sub-dir.

febbraro’s picture

Status: Active » Fixed

Ok, this is now in the alpha8 release.

pcwick’s picture

deleted

Status: Fixed » Closed (fixed)
Issue tags: -Libraries

Automatically closed -- issue fixed for 2 weeks with no activity.