Sujet : Re: Software Engineer Seeks Compatible Cratifier
De : simon (at) *nospam* pushface.org (Simon Wright)
Groupes : comp.lang.adaDate : 18. Jun 2024, 23:12:15
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <lyfrta7y6o.fsf@pushface.org>
References : 1 2 3 4
User-Agent : Gnus/5.13 (Gnus v5.13)
Pascal Obry <
pascal@obry.net> writes:
Le mardi 18 juin 2024 à 20:06 +0200, Jeffrey R.Carter a écrit :
IIUC, there has to be a project file in the crate. That does not mean
there has to be a project file in my Github repository.
>
But then you impose someone to create a project file. And this would be
needed by all packager, there is not only crates around to build a
component. And moreover, you let the "packager" find the correct
options to be used which is certainly not a good solution.
>
That's exactly why I had proposed a PR with a project file. It
"documents" the way the code must be compiled (at least with GNAT) and
installed for everyone wanting to package your components.
The crate in the index contains (amongst other things) the name of the
.gpr and a link to the source; e.g.
project-files = "minimal_containers.gpr"
[origin]
commit = "592661c64b8ad6fa40864e9584a8faa3a1d2b283"
url = "git+
https://github.com/simonjwright/minimal_containers.git"
The project file is in the source.
It would be possible to 'cratify' the PragmaARCs by forking the repo and
adding an alire.toml and a .gpr - which would be very simple if there
was no particular need for special compilation switches (and one
wouldn't need compile_all.adb). But it would feel a bit daunting without
a helpful README.