void-linux / void-linux/void-packages

Package request: udunits

Open
#40,816 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

request
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Package name

udunits

Package homepage

https://www.unidata.ucar.edu/software/udunits/

Description

udunits provides a C library for units of physical quantities and a unit-definition and value-conversion utility. It comes as a system requirement/dependency for another R package which is a dependency for ggplot2/ggthemes; it's a dependency for units.

Firstly, this should be a library package (libudunits), right?

I just had issues with the license and building

  1. nowhere does it state what license it uses and only has a file called COPYRIGHT that has a similar declaration to the MIT license
  2. while building, the configure build-helper complains that
=> ERROR: udunits-2.2.28_1: /builddir directory is not allowed, remove it!

Not sure how to proceed. Could I perhaps open a PR and work from there? Better yet, I'll jump onto the IRC channel and get help there.

Does the requested package meet the package requirements?

Compiled

Is the requested package released?

Yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the udunits homepage and inspect its COPYRIGHT file to establish the applicable license. Reproduce the configure error involving /builddir, then compare the package request with existing Void package conventions; done means a valid udunits package builds successfully and satisfies the stated compiled-package requirements.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
build-system
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.