Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
dune-common
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 69
    • Issues 69
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 45
    • Merge Requests 45
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Core Modules
  • dune-common
  • Issues
  • #221

Closed
Open
Opened Oct 18, 2020 by Christoph Grüninger@gruenichOwner

Future direction of dunecontrol

In #200 (closed) a discussion about the future of dunecontrol started. I want to move the discussion here for better documentation and referencing.

There are two main directions, which I sense:

  • Add features to dunecontrol to help users. The are handy to use and easy to teach.
  • Try to reduce dunecontrol and make the use more compatible to to the way Compilers, CMake and Make are used in the world outside of Dune. Then users can more easily use the advice they find on Stackoverflow or what they are used from other projects.
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: core/dune-common#221