On 01/12/2016 09:19, Thomas Gazagnaire wrote:
>> - mirage configure should recompile the configuration
>> according to
>> - mirage build should build, and error out if the unikernel was not
>> configured upfront
>
> How do you work with multiple target/config in parallel with this workflow?
>
On Thursday, 01.12.2016 at 09:19, Thomas Gazagnaire wrote:
> > - mirage configure should recompile the configuration
> > according to
> > - mirage build should build, and error out if the unikernel was not
> > configured upfront
>
> How do you work with multiple target/config in parallel with
On Thursday, 01.12.2016 at 19:10, Drup wrote:
>
> >I'm now wondering: what was the rationale for having `mirage describe`
> >vs `mirage help` at all?
> >Maybe it would be better to incorporate the tty-output options of
> >`describe` into the `help` output, and have `mirage describe` only
>
I'm now wondering: what was the rationale for having `mirage describe`
vs `mirage help` at all?
Maybe it would be better to incorporate the tty-output options of
`describe` into the `help` output, and have `mirage describe` only
produce the `--dot` output using the cached result of `mirage
On 30 November 2016 at 18:43, Hannes Mehnert wrote:
> cc'ed mirageos-devel again
>
> On 30/11/2016 18:37, Sean Grove wrote:
>> Thanks so much for going over this with a fine-toothed comb, I love the
>> idea of the whole process being smoother.
>
>
> And your feedback is
On 11/30/2016 12:28 PM, Hannes Mehnert wrote:
I'm not yet happy with the workflow.
What I'd like to have:
- mirage help should be executable with and without a config.ml -- if
config.ml is present, compile it to show possibilities
- mirage describe should work with and without a configured
> - mirage configure should recompile the configuration
> according to
> - mirage build should build, and error out if the unikernel was not
> configured upfront
How do you work with multiple target/config in parallel with this workflow? Do
you need to reconfigure if want to switch between
On Wednesday, 30.11.2016 at 11:35, Richard Mortier wrote:
> On 30 November 2016 at 11:32, Martin Lucina wrote:
> > 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
On 30 November 2016 at 11:32, Martin Lucina wrote:
> 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 useful
>> to *not* have to run
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 useful
> to *not* have to run `mirage configure` first and actually set those
> options explicitly?
Isn't
[ May not be able to make the call tonight, so in lieu of that my
responses to Martin's questions below ]
On 30 November 2016 at 11:09, Martin Lucina wrote:
...
> I'd also like to propose/discuss the following followup changes:
>
> 1. Now that we have more targets for Mirage
On Monday, 28.11.2016 at 15:14, Hannes Mehnert wrote:
> On 25/11/2016 18:26, Hannes Mehnert wrote:
> > It does not yet work completely (clean seems to be broken), but please
> > provide feedback on https://github.com/mirage/functoria/pull/84 and
> > https://github.com/mirage/mirage/pull/703
>
>
On 25/11/2016 18:26, Hannes Mehnert wrote:
> It does not yet work completely (clean seems to be broken), but please
> provide feedback on https://github.com/mirage/functoria/pull/84 and
> https://github.com/mirage/mirage/pull/703
Update: works now! Travis job which compiles mirage-skeleton on
13 matches
Mail list logo