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,de92eb048dc3c019 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.scarlet.biz!news.scarlet.biz.POSTED!not-for-mail NNTP-Posting-Date: Mon, 20 Mar 2006 05:55:05 -0600 From: Ludovic Brenta Newsgroups: comp.lang.ada Subject: Re: Library file locations (was: Debian Policy for Ada, Second Edition) References: <87hd5u843z.fsf@ludovic-brenta.org> Date: Mon, 20 Mar 2006 12:51:18 +0100 Message-ID: <87acbl8hc9.fsf@ludovic-brenta.org> User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux) Cancel-Lock: sha1:b4T0F5w7xx5V/hjW1pwLzpiP0G4= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: 83.134.238.138 X-Trace: sv3-KpAGu32M7VBwW5w/hzATIuVHEapTNO+NsWVzzRl/c9i4IX5ofwQitetciiJ8ffL2St6QbO90rSYcZ6n!9BaIorkpx5D9BlVPRlSB4I2PMaCojtVAc0IAuenNcm/YgYj2ILCOrvjjm2DzhxFAzFCr0hKD9Us= X-Complaints-To: abuse@scarlet.be X-DMCA-Complaints-To: abuse@scarlet.biz X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 Xref: g2news1.google.com comp.lang.ada:3482 Date: 2006-03-20T12:51:18+01:00 List-Id: Tapio Kelloniemi writes: >>In particular, /usr/local is, by definition, for use by the system >>administrator, and therefore falls outside the scope of any policy >>defined by the operating system. > > Why GCC then looks for headers in /usr/local/include? Because many packages > are installed in /usr/local by sysadmins and because /usr/local/include > is in GCC's default search path, other packages can link against > packages installed by admin without using absolute paths. Has anyone ever > seen C code like: > #include "/usr/local/include/readline/readline.h" No but I often see: gcc -c -I/usr/local/include foo.c > What comes to setting ADA_PROJECT_PATH, I think it is just setting > one more redundant environment variable. Editing a text file is much > more elegant solution. But you would normally set ADA_PROJECT_PATH from within a Makefile, so your objection is weak. >> If you want GNAT to look in some >>particular subdirectory of /usr/local, then use ADA_PROJECT_PATH or >>"with" the fully qualified file name of your project files. > > Let us think that I'm to publish my application A in source format on my > web site. The package is built with a command like: > gnatmake -PA > > If my project file contains something like: > with "/usr/share/ada/adainclude/florist.gpr"; > with "/..."; > with "/..."; > > Suddenly I'll get a lot of complaints that compiling my application is very > frustrating because users must hassle with the absolute path definitions > in my project file. As I said, gnat-4.1 will look in /usr/share/ada/adainclude by default, so you will not need absolute paths. So your objection is addressed. Secondly, even if gnat didn't look in that directory by default, nobody could blame you for following the GNAE standard, could they? >>So, what exactly is the problem? > > Easy usage of libraries, no matter whether they are installed by a > sysadmin or a distro. And the Debian Policy for Ada addresses just that problem. I meant, what is the *remaining* problem after you've read the Debian Policy for Ada? -- Ludovic Brenta.