[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] build workflow

On November 30, 2016 5:44:42 AM CST, Martin Lucina <martin@xxxxxxxxxx> wrote:
>On Wednesday, 30.11.2016 at 11:35, Richard Mortier wrote:
>> On 30 November 2016 at 11:32, Martin Lucina <martin@xxxxxxxxxx>
>> > On Wednesday, 30.11.2016 at 11:25, Richard Mortier wrote:
>> >> I thought one of the things `mirage describe` could do was display
>> >> information about possible configuration options -- ie., it's
>> >> to *not* have to run `mirage configure` first and actually set
>> >> options explicitly?
>> >
>> > Isn't that what "mirage configure --help" is for?
>> I thought `describe` gave the .dot output, visualising the configure
>> graph too (but before it was constrained by the configure options the
>> user specifies)?
>That's one of the things it does, if you ask for it with "--dot".
>it with no arguments gives output like this:
>Name       stackv4
>Root       /home/mato/solo5/mirage-skeleton/stackv4
>Keys       dhcp=false (default), gateway= (default),
>interface=tap0 (default), interfaces= (default), logs=
>net=direct (default), network= (default), prng=stdlib
>  socket= (default), target=unix (default), warn_error=false (default)
>MirageOS-devel mailing list

Running `mirage describe --eval` considers the values of keys and collapses the 
graph as appropriate -- perhaps that's what you're looking for?
composed on a touchscreen keyboard; please forgive typos and brevity

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.