See: https://tada.pm
Nice.
Do you have any plans for further development?
Yes, I do! Tada is usable as-is right now, but I still want to:
- Implement better toolchain management - right now Tada expects you to have gnat and gprbuild installed, you can configure different toolachains, but thatās a manual step
- MOAR PACKAGES!!11
- thatās what Iām working on 
- Once there is more packages - better dependency graphs
- Once there is more packages - packages index querying, etc.
Ada has a 2nd package manager?
Crazy times, huh?
I built one for myself, ābecause I canā. Not planning to harm Alire in any way (itās wonderful it exists!)
At least three: this thing, Alire, and Aura
To be honest I donāt understand your position here. You say you make this project for yourself, or on the website āTada is a project for personal useā. But you post about it a lot (on this forum, reddit, etc.), and you create a website. So it seems you want other people to use it.
I think this is harming the Ada community more than Alire. Like when I see your Tackle, or padlock projects not available to the community, I canāt help to think this is a shame.
I agree with Fabien here. I fear that something similar might happen like in Haskell. They have one package repo but 2(,5?) package managers (Cabal v1/v2 and Stack) and for beginners it causes a lot of confusion. Especially for preconfigured tools and editors. In my case Doom Emacs is preconfigured for cabal but I use stack.
Please donāt⦠As someone who is working to get a SuperH cross compiler working with Alire, I can tell you that toolchain management is hard. You would have build and package the tools. If you decide to use the tools from gnat-fsf-builds what actual benefit do you get? Not only do you have to set your default toolchain (presumably gnat_native) but also per project configuration and their .gpr files (Especially Runtime and Driver).
Could you also package your crates for alire?
I donāt mean to sound mean. Tada is a cool project. Itās just that long term it might result into a haskell situation which would be less than ideal ![]()
I feel torn between cheering for your enthusiasm and voicing my concerns about fragmentation (as others already have). ![]()
Keep doing whatever you find useful.
Thanks! This looks really cool. Appreciate all the hard work!
Might I suggest, before jumping down āmore content!ā, that you prioritize #4 & #3.
Iām of the opinion the best way to do this would be via a database amiable IR, not ātextā or āfilesā; it is more up-front and design heavy work, but the payoff is things like:
- No uncompilable (or at least unparsable) packages.
- You already have the DB to manage metainfo, like licenses and dependencies.
- You can design the system to validate, via query, the combinations of various packages.
Honestly, this is one area Iād like to address ā bootstrapping an Ada compiler, one that is formally verified, should be a matter of āfollow this recipe/procedureā, a triviality.