Skip to content
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

fixes #4174 - fixed locale distribution and jenkins rake task #50

Merged
merged 1 commit into from Jan 24, 2014

Conversation

lzap
Copy link
Member

@lzap lzap commented Jan 24, 2014

Two issues from RC1 resolved plus i18n support is fully working now. Although
i18n plugin support does not support javascript and model localization, we do
not use these in Discovery.

Also, there is a PR coming to Foreman with minor changes in the Makefile script
to better support plugin extraction.

Packagers note: Please do this command during package build to prepare MO
files:

make -C locale all-mo

That should create locale/*/LC_MESSAGES/discovery.mo files.

@GregSutcliffe
Copy link
Member

@lzap so that needs to go in the debian package for the discovery plugin?

@domcleal looks ok to me but I know little about i18n, could you ack?

@domcleal
Copy link

👍 all present and correct.

I guess you'd need to run the make before building the gem and distribute .mo files with it?

@lzap
Copy link
Member Author

lzap commented Jan 24, 2014

Exactly, just run the above command in your "SPEC" file, I guess it's "rules" file.

I'll go ahead and modify our RPM file for rc2 once it is out. @domcleal not releasing workarounded RPM as Greg plans to release rc2 quite soon I guess.

@domcleal
Copy link

Debian uses the packaged gems, and surely other users who apply just the rubygem will need the .mo files? So it seems to me they should packaged in the .gem, not built in the RPM or Debian package - because the .gem is also an end user binary package.

@GregSutcliffe
Copy link
Member

@domcleal I think I agree, it needs to be in the gem. @lzap care to add that to this PR? Or shall I figure out where that needs to go? :)

@lzap
Copy link
Member Author

lzap commented Jan 24, 2014

Hmmm I say yes to MO files in the gem file, but NO to MO files in the
git :-)

Can you just create a ./release.sh with the make file from above and
"gem release discovery.gemspec"?

Later,

Lukas "lzap" Zapletal
irc: lzap #theforeman

@GregSutcliffe
Copy link
Member

I agree, we don't want them in git, just in the gem.

@lzap
Copy link
Member Author

lzap commented Jan 24, 2014

FYI its already in gitignore, so you really only need to generate them
and include them. I guess it will be included automatically as the whole
locale/*/ is there.

Really just the two commands, go ahead!

Later,

Lukas "lzap" Zapletal
irc: lzap #theforeman

@GregSutcliffe GregSutcliffe merged commit a27a232 into theforeman:develop Jan 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants