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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,d99dc61bb22990d2
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!k38g2000vbn.googlegroups.com!not-for-mail
From: Ludovic Brenta <ludovic@ludovic-brenta.org>
Newsgroups: comp.lang.ada
Subject: Re: Packaging and linking shared Ada libraries
Date: Tue, 8 Mar 2011 02:48:34 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <68895e03-b4d7-44a8-b356-c9bfeda0c78a@k38g2000vbn.googlegroups.com>
References: <4d746dde$0$10593$742ec2ed@news.sonic.net>
 <m2zkp7v1tx.fsf@pushface.org>
 <4d75245e$0$22170$742ec2ed@news.sonic.net>
NNTP-Posting-Host: 153.98.68.197
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1299581314 27093 127.0.0.1 (8 Mar 2011 10:48:34
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 8 Mar 2011 10:48:34 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: k38g2000vbn.googlegroups.com; posting-host=153.98.68.197;
 posting-account=pcLQNgkAAAD9TrXkhkIgiY6-MDtJjIlC
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6)
 Gecko/2009012111 Red Hat/3.0.6-1.el5 Firefox/3.0.6,gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:17964
Date: 2011-03-08T02:48:34-08:00
List-Id: <comp.lang.ada>

R Tyler Croy wrote on comp.lang.ada:
> Looking at some of Ludovic's packages, he's actually defined a debian build
> .gpr file and adds a Makefile to use that .gpr to build, then place the files
> he needs in the appropriate directories. I'm following a similar approach.

Right.  The Makefile is part of the Debian automated build
infrastructure and it is mandated by the (general, not Ada-specific)
Debian Policy.  The part about "plac[ing] the files [I] need in the
appropriate directories" deserves a bit more explanation.  Remember
that this is in the context of a binary distribution where the person
building the package (me) is not the same as the person who will later
use the package.

So, in this context, the "appropriate directories" are system-wide
(not in a user's home directory), under control of the package manager
(dpkg in the case of Debian) and not writable by the end user.

The solution suggested by Simon is only appropriate for a source
distribution where the end user is also a system administrator and has
write privileges in the compiler installation directories.

--
Ludovic Brenta.