New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install Ruby mapscript in sitearchdir instead of archdir. #4754

Merged
merged 1 commit into from Sep 18, 2013

Conversation

Projects
None yet
3 participants
@sebastic
Contributor

sebastic commented Sep 11, 2013

This change complements #4749. Installing the Ruby mapscript library in /usr/lib/ruby// is wrong, while Debian packages installed modules there this is not correct for MapServer upstream.

The installation directory is changed to /usr/local/lib/ruby/site_ruby//, quite similar to the Perl mapscript installation directory /usr/local/lib/perl/5.14.2.

The Debian packages modify CMakeLists.txt to use vendorarch instead to install in the /usr prefix instead of /usr/local.

sdlime added a commit that referenced this pull request Sep 18, 2013

Merge pull request #4754 from sebastic/ruby-mapscript
Install Ruby mapscript in sitearchdir instead of archdir.

@sdlime sdlime merged commit 42733c2 into mapserver:master Sep 18, 2013

1 check passed

default The Travis CI build passed
Details
@sdlime

This comment has been minimized.

Show comment
Hide comment
@sdlime

sdlime Sep 18, 2013

Member

@sebastic or @tbonfort, should this also be applied to branch-6-4?

Member

sdlime commented Sep 18, 2013

@sebastic or @tbonfort, should this also be applied to branch-6-4?

@tbonfort

This comment has been minimized.

Show comment
Hide comment
@tbonfort

tbonfort Sep 18, 2013

Member

crap, I let this one through... cherry-picked for 6.4.1 in a70d192

Member

tbonfort commented Sep 18, 2013

crap, I let this one through... cherry-picked for 6.4.1 in a70d192

@ghost ghost assigned tbonfort Sep 18, 2013

@sebastic sebastic deleted the sebastic:ruby-mapscript branch Jan 25, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment