First beta release of Alire, the package manager for Ada/SPARK
blog.adacore.com
First beta release of Alire, the package manager for Ada/SPARK
1–10 of 22 posts
Re: First beta release of Alire, the package manager for Ada/SPARK
#2This seems useful. One thing Ada has been lacking is a central place to upload and use dependencies.
However, I’ve found that pure Ada code without a package manager is pretty easy to integrate using the gprbuild tool; you just copy the dependency’s .ads and .adb files into your project and add their enclosing folder to the list of source directories. gprbuild figures our how to build them pretty much automatically.
So I wish that instead of using TOML files, the dependencies would be specified in the gprbuild project files themselves. The syntax/options of GPR files would probably have to be extended, but it would be nice to have only one layer of config files that contains everything needed to build an Ada library/project.
Re: First beta release of Alire, the package manager for Ada/SPARK
#3This seems useful. One thing Ada has been lacking is a central place to upload and use dependencies. However, I’ve found that pure Ada code without a package manager is pretty easy to integrate using the gprbuild tool; you just copy the dependency’s .ads and .adb files into your project and add their enclosing folder to the list of source directories. gprbuild figures our how to build them pretty much automatically.…
How do you deal with versioning, etc?
Re: First beta release of Alire, the package manager for Ada/SPARK
#4This seems useful. One thing Ada has been lacking is a central place to upload and use dependencies. However, I’ve found that pure Ada code without a package manager is pretty easy to integrate using the gprbuild tool; you just copy the dependency’s .ads and .adb files into your project and add their enclosing folder to the list of source directories. gprbuild figures our how to build them pretty much automatically.…
How do you deal with versioning, etc?
GPR project files are just a kind of config file. Their syntax is different than TOML files, but they could easily be given the capability to list dependencies and versions.
Re: First beta release of Alire, the package manager for Ada/SPARK
#5Is Ada a staticly linked language?
Re: First beta release of Alire, the package manager for Ada/SPARK
#6Is Ada a staticly linked language?
The GNAT compiler (part of GCC) supports both static and dynamic linking.
Re: First beta release of Alire, the package manager for Ada/SPARK
#7This is a great thing for the Ada community. I hope this encourages more contribution and collaboration on libraries that keep Ada useful for mainstream development.
Re: First beta release of Alire, the package manager for Ada/SPARK
#8This seems useful. One thing Ada has been lacking is a central place to upload and use dependencies. However, I’ve found that pure Ada code without a package manager is pretty easy to integrate using the gprbuild tool; you just copy the dependency’s .ads and .adb files into your project and add their enclosing folder to the list of source directories. gprbuild figures our how to build them pretty much automatically.…
I agree, put it all in GPR files, no more makefiles, bash scripts. I'd go even further, make project extensions able to define build variables, so I have no more to type -X options...
And with the GPR handling libraries and Libadalang there's already so much you can do...
Re: First beta release of Alire, the package manager for Ada/SPARK
#9Is Ada a staticly linked language?
All compiled programming languages have supported static linking since the early days, then dynamic linking came into mainstream during the 90's, and most toolchains added support for both models, including Ada compilers.
Re: First beta release of Alire, the package manager for Ada/SPARK
#10All I hope is that they'll think about corporate firewalls and provide a simple way to mirror the whole thing (including their gnat-subscriber-only & tools&libs versions). Or at least provide some kind of Web page with all the download links for the transitive dependencies for a package...
PYPI kills me everytime I need to run any ML stuff, and I wish there was a systematic page to d/l all transitive dependencies (at least from requirements files and maybe setup.py static interpretation...)