Alejandro R Mosteo

I see your point. I don't really know what is better, as preelaborable packages can help in reducing elaboration circularities. Perhaps also adding some comment that it is perfectly OK...

> The message has duplicate, and what look like debugging information. This is a legitimate problem in how our scoping of errors works right now. It should be possible to...

Might be related to the new configuration of builds in which we build all dependencies in release mode by default? With what `alr` version are you seeing this?

OK, so compiler-specific. Thanks for the info.

Related to #624

Yes, this is in the spirit of the idea. Also `alr with` could warn/fail when you try to add an incompatible-licensed dependency to the ones already in use.

Hi @pjljvandelaar, thanks for your interest in contributing to the Alire ecosystem. For 1) and test cases, it is enough that you don't list their project file in the alire...

Thanks for the report, @rocher. Indeed improving automation and simplifying user experience is always worthwhile. This is now in our radar thanks to your report. In regard to the particular...

Seems sensible to me. Certainly what we have now is old from the early days IIRC.

This is a "soft" error in the sense that the check is done locally in your computer, because we want to encourage all new submissions to contain a manifest remotely...