Dear Alire developers,

We are considering whether we should switch to alire for
https://github.com/TNO/Renaissance-Ada/
Unfortunately, the documentation of Alire is not yet finished.

We ran in a few problems where we can't find an answer for in the documentation.

1. Many of our projects:
   see e.g. https://github.com/TNO/Renaissance-Ada/tree/main/src/libraries/Rejuvenation_Lib
   have two project files:
   one for building and one for testing.
   From the documentation it is unclear to us, how we should deal with these test cases.
   What solution do you recommend?

2. Consistency between flags and options between projects is important.
   We realize this using the standard_options project (https://github.com/TNO/Renaissance-Ada/blob/main/src/standard_options.gpr).
   We like that all flags and options are localized at a single place.
   We see that alire generates gpr files where these flags and options are duplicated.
   Would you recommend to abandon our approach in favor of alire's approach to better fit in the alire environment/ecosystem?

3. We have a single aggregate project such that we can build, test, generate documentation etc. with a single command.
   How should we realize this with Alire?

4. We have a super project that contains multiple smaller, related projects.
   We have the impression that Alire recommends a github project for each (small) project.
   Is this indeed the recommended practice for Alire?

Thanks in advance for your answers