mesonbuild / mesonbuild/meson

Make - and _ synonyms in project options and enforce a convention for option names

Open
#2,186 0 comments 2 reactions 0 assignees View on GitHub
enhancement options
Dominant language
Python
Stars
6.6k
Forks
1.9k
Avg merge
2d 6h
Merged PRs (30d)
33

Description

Since we didn't specify a convention, people have been inconsistently using `-` or `_` in different projects for options. This is particularly annoying in umbrella projects like GNOME where support for the same library is under different options in different projects.

I also think we should decide on a convention for meson options, provide a way to migrate options (via an alias that either warns or errors), and enforce it. For instance, options must not start with enable/disable or with/without since those are redundant. You need those in Autotools because it does not have 'types' for option values, but we do.

We should do this sooner rather than later.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by surveying Meson’s project-option parsing and validation; done would require an agreed naming convention, a migration alias that can warn or error, and enforcement against redundant enable/disable or with/without prefixes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.