From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Received: by 2002:a6b:c786:: with SMTP id x128-v6mr19060104iof.1.1539068629299; Tue, 09 Oct 2018 00:03:49 -0700 (PDT) X-Received: by 2002:aca:3094:: with SMTP id w142-v6mr431993oiw.0.1539068629023; Tue, 09 Oct 2018 00:03:49 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.166.215.MISMATCH!z5-v6no23070ite.0!news-out.google.com!n199-v6ni59itn.0!nntp.google.com!z5-v6no23067ite.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 9 Oct 2018 00:03:48 -0700 (PDT) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=62.121.55.154; posting-account=9KbC2woAAAA0kK2IAUr3-FkzJBtOzrhm NNTP-Posting-Host: 62.121.55.154 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <84ec9c9b-0c32-40da-998f-8a5ad122f243@googlegroups.com> Subject: Per-project third party library management From: =?UTF-8?B?SGVucmlrIEjDpHJrw7ZuZW4=?= Injection-Date: Tue, 09 Oct 2018 07:03:49 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:54520 Date: 2018-10-09T00:03:48-07:00 List-Id: What would be the most convenient way to manage ( mostly install & upgrade)= a third party library for one's project? With python projects I'd probably fire up an virtualenv per project and ins= tall stuff there with pip etc. With scala I'd use SBT to handle the librari= es. In my C development days, we had a proprietary RTOS with all of it's de= pendencies managed by someone else, so I didn't have to (or get to learn) w= orry about those personally... :( As I've understood, Ada doesn't have such a package distribution system, so= one would typically download sources, compile and install the library thro= ugh it's make system. Or install readily packaged version of the library, f= or example with apt-get etc. So far, I've installed AWS from source and Ahven from a DEB package, and as= such they are just fine methods. But both were using root access and syste= m wide install. What I'm aiming for with my question, is to learn a way to install a librar= y so that it would not require root access and it would be more tied to the= project.=20 Different projects might need to use different versions etc. Should I use GNU Stow, or configure --prefix to point somewhere under my pr= oject tree and have gprbuild include it from there, or...? My apologies if this has been asked a lot, but at least I didn't find that = many directly related discussions about this. -Henrik