Allow admin to specify where perl modules will be installed
Bug #1631520 reported by
Mike Rylander
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenSRF |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
Today, one cannot specify where the perl modules for OpenSRF will land, as one can do with the C libraries. This would benefit environments with shared installation directories.
Here's a branch that attempts to do this:
(I have a similar branch for Evergreen, which I'll post there after any cleanup identified by this branch can be made to the other.)
| Changed in opensrf: | |
| status: | New → Confirmed |
| milestone: | none → 2.5-alpha |
Revision history for this message
| Galen Charlton (gmc) wrote | #1 |
| Changed in opensrf: | |
| status: | Confirmed → Fix Committed |
| Changed in opensrf: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Pushed to master for inclusion in 2-5-alpha with a fair number of tweaks to the commit message. Thanks, Mike!