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

Update udunits to 2.2.x branch #847

Closed
durack1 opened this issue Oct 24, 2014 · 11 comments
Closed

Update udunits to 2.2.x branch #847

durack1 opened this issue Oct 24, 2014 · 11 comments

Comments

@durack1
Copy link
Member

durack1 commented Oct 24, 2014

We are a minor release behind the udunits latest (2.1.24 vs 2.2.17). I also note that they've migrated across to a git repo: https://github.com/Unidata/UDUNITS-2, switching to this would avoid having to manage the source tar balls

@doutriaux1 @aashish24 want to assign this task as a 2.1 milestone?

@doutriaux1
Copy link
Contributor

please test before submiting, I vaguely remmber switching to the newer one and not pushing this thorugh, there's probably a good reason....

@aashish24
Copy link
Contributor

assigned to @durack1

@durack1
Copy link
Member Author

durack1 commented Oct 29, 2014

@doutriaux1 ok source was already updated at the ${LLNL_URL} - you just hadn't tested 2.2.17?

This was referenced Nov 11, 2014
@durack1
Copy link
Member Author

durack1 commented Nov 24, 2014

@doutriaux1 @aashish24 can you mark this as a 2.2 milestone please?

@doutriaux1 doutriaux1 added this to the 2.2 milestone Nov 24, 2014
@alliepiper
Copy link
Contributor

@jbeezley @durack1 @aashish24 @doutriaux1

Removing the patch step breaks compilation on travis builds. Ref #769.

The patch just drops in a new configure script that removes the checks for flex (as detection is broken on the travis builds and udunits doesn't actually use any lexers, anyway).

Looks like a new patched configure file is needed for the new version.

@aashish24
Copy link
Contributor

@dlonie can push a brach with the fix?

@aashish24
Copy link
Contributor

Actually the new udunits should have CMake. May be we should use it instead?

@alliepiper
Copy link
Contributor

Sure, I'll look into it.

On Wed, Jan 21, 2015 at 9:42 AM, Aashish Chaudhary <notifications@github.com

wrote:

Actually the new udunits should have CMake. May be we should use it
instead?


Reply to this email directly or view it on GitHub
#847 (comment).

@durack1
Copy link
Member Author

durack1 commented May 6, 2015

@doutriaux1 wanna add the enhancement label (for @chaosphere2112's readme: #913)

@doutriaux1
Copy link
Contributor

done and you now have permissions to add labels on the repo, so feel free to do it.

@durack1
Copy link
Member Author

durack1 commented May 6, 2015

@doutriaux1 currently doing that now.. thanks..

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

No branches or pull requests

4 participants