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

Schedule for new minor release of muparserx? #45

Closed
GoogleCodeExporter opened this issue Mar 22, 2015 · 2 comments
Closed

Schedule for new minor release of muparserx? #45

GoogleCodeExporter opened this issue Mar 22, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

Hi,

I'm curious to know if there is any plan to release a new version for muparsex 
(minor release). We're using the library in the ORFEO ToolBox and there are 
patchs which were added to muparserx after last release. Currrently we're 
relaying on the trunk to make it works with OTB. It could facilitate if we can 
provide directly a pointer to a source package

Don't know if there are major ongoing issues which block this.

Thank you in advance.

Best regards,

Manuel


Original issue reported on code.google.com by manuel.g...@gmail.com on 16 Mar 2015 at 3:04

@GoogleCodeExporter
Copy link
Author

I will create a new binary archive soon. But i'm not sure whether i will 
continue to make "official" trarballs since google is going to pull the plug on 
google code and i have to migrate to github. At github you have the option to 
get the head revision as an archive anyway.

Original comment by ib...@gmx.info on 20 Mar 2015 at 8:58

@GoogleCodeExporter
Copy link
Author

Thanks for your answer, 

For now we are using cmake external project mechanism to download and install 
muparserx in orfeo toolbox, official source release will allow to install the 
package without having to install subversion. 

Making official source tarballs on sourceforge for instance can help also later 
packaging effort of muparserx on Linux distrib.

Agree also with you that you should move from google code...

Thanks again.

Manuel


Original comment by manuel.g...@gmail.com on 20 Mar 2015 at 1:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants