From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-65-14.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 Path: eternal-september.org!reader01.eternal-september.org!aioe.org!gy7opw3oYmwPg+L8gXeD2w.user.46.165.242.75.POSTED!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: yet another Ada web site? Date: Wed, 12 Oct 2022 17:06:26 -0700 Organization: Aioe.org NNTP Server Message-ID: <861qrch9j1.fsf@stephe-leake.org> References: <8635bxht60.fsf@stephe-leake.org> <12faec32-1572-4df5-af28-be1c41083b9cn@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: gioia.aioe.org; logging-data="55592"; posting-host="gy7opw3oYmwPg+L8gXeD2w.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org"; User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (windows-nt) Cancel-Lock: sha1:0jqMfMp49C2/MRMyf+dXkp5yRvU= X-Notice: Filtered by postfilter v. 0.9.2 Xref: reader01.eternal-september.org comp.lang.ada:64493 List-Id: Paul Jarrett writes: >> I am not sure if package manager is a good idea if it does not refer the >> target system's packaging tools, e.g. DEB, RPM, MSI etc. Alire can define crates that import system libraries, using those tools. They are subject to the same version checks as other Alire crates. >> The main problem with that stuff is usually architectural. Most of it is > plain aggregation of source code, which is utterly wrong. >> >> The very idea to rebuild everything each time on each client is >> atrocious both with regard of wasting computing resources as well as >> testing, safety, consistency, interoperability inside the target. Actually, it's better for consistency; that's why Alire does it. I don't understand what you mean by "testing" here; how does compiling from source affect testing? Same for "interoperability". > I've seen inconsistencies in builds when developers who rely on the > system libraries (installed by things like apt) join the project at > different times -- the earliest developers might be on libfoo-1.2 > whereas newer developers are on libfoo-1.4. You don't run into this > problem if the repo points to the applicable dependencies and everyone > builds everything locally. More precisely, an Alire crate can specify precisely which version of each dependency it requires/is compatible with. -- -- Stephe