Mir

[enhancement] It should be possible to customize configuration options without going via boost options and the commandline

Bug #1351255 reported by Alan Griffiths
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Wishlist
Alan Griffiths
0.6
Fix Released
Wishlist
Alan Griffiths
mir (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Shells will typically want to handle their own command line and pass some options to Mir and not need to provide Mir with a command line to parse. (Unity8 would want to use QCommandLineParser for example.)

There is some separation into the mir::options but there's no effective support for building a replacement for DefaultConfiguration on top of another parsing technology.

Tags: enhancement

Related branches

Revision history for this message
Gerry Boland (gerboland) wrote :

Agreed. We would very much like that we can combine Qt's and Mir's command line parsing and help output in a way that makes sense.

If Mir could offer a method which we pass command line arguments, and it returns a command line argument list with the mir recognised entries removed, it would help a lot.

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

Gerry, I was thinking of a very different approach:

That there could be a way to programmatically determine the options Mir supports (and their corresponding defaults) and that clients should be able to build an Options object using their own parsing of command-line, environment and/or config files.

It would certainly be simpler to focus on the command-line only and allow that to be "partitioned".

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: New → Fix Committed
Changed in mir:
milestone: none → 0.7.0
Changed in mir:
milestone: 0.7.0 → 0.6.0
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix backported to lp:mir/0.6 at revision 1834.

Changed in mir:
milestone: 0.6.0 → 0.7.0
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

mir (0.6.0+14.10.20140811-0ubuntu1) utopic; urgency=medium

Changed in mir (Ubuntu):
importance: Undecided → Wishlist
status: New → Fix Released
Changed in mir:
milestone: 0.7.0 → none
status: Fix Committed → Fix Released
Changed in mir:
milestone: none → 0.7.0
status: Fix Released → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry for the confusion. Most of the 0.7.0 series got merged into 0.6.0 at a late stage. I've verified everything in 0.6.0 is also fixed in 0.7.0. So although the branched fixes in 0.7.0 have not been "released" yet, the equivalent fixes in 0.6.0 have. No need to mention them in 0.7 any more.

Changed in mir:
milestone: 0.7.0 → none
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.