4 ms·
> How difficult is to make a `yarn && yarn build`? Not difficult, but not necessary either. I could also figure out how to build the XCP-ng ISO myself, but I
by pikdum 4y ago
> How difficult is to make a `yarn && yarn build`?
Not difficult, but not necessary either. I could also figure out how to build the XCP-ng ISO myself, but I think everybody uses the builds you provide instead.
> Again, most of what you see now is in transition before a clearer model since we have the whole stack control :)
Good to hear, looking forward to see what you guys come up with.
- plam503711 4y agoI understand your point. However, anything else might require time to maintain it (a script, a container, a VM, whatever you want: people will expect it to work obviously, so this needs time/effort to test it, unlike a simple documentation). Do we want to maintain that? I'm not sure due to the huge backlog and higher priorities. But I'm eager to have more resources to change that in the future :) (all things considered, an official "community" container might be the easiest path, but we'd like to have maintainers outside Vates)