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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Ada package registry? Date: Sun, 31 Jan 2016 17:21:48 +0100 Organization: Aioe.org NNTP Server Message-ID: References: <02241ec4-0f95-4f63-9abc-092f167eb59e@googlegroups.com> <86a8nlg305.fsf@gaheris.avalon.lan> NNTP-Posting-Host: LNA1TkTuMxfwTHzeJdi6nA.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:29305 Date: 2016-01-31T17:21:48+01:00 List-Id: On 2016-01-31 16:52, Mart van de Wege wrote: > "Dmitry A. Kazakov" writes: > >> On 2016-01-30 23:14, Tero Koskinen wrote: >> >>> Usually the repositories are maintained in "wiki"-style and anyone can >>> update the package details (within certain limits). This causes some >>> security concerns/implications, but in general there is not that much >>> abuse and the repositories work well enough. >>> >>> The package repository management tool is used like this: >>> >>> $ language_package_mananager install X >>> Downloading dependencies for 'X', please wait a while... >>> Downloading X... >>> Package 'X' installed! >>> $ >> >> Yes, the problem is to have it working. >> >>> Once the package (a library usually) is installed (to your home >>> directory), you can link it to your program and simply use it. >> >> No, that the point. It cannot be installed in your home directory. It >> must be in the directories mandated by the target system >> policy. E.g. for Debian Linux: >> >> https://people.debian.org/~lbrenta/debian-ada-policy.html#Files-provided-by-the-_002ddev-package >> > Nope. There is no use in a repository that does not follow the target platform policy. > Managing ADA_INCLUDE_PATH in an Ada equivalent would not be much > different. ADA_INCLUDE_PATH is not enough and of no use anyway because there is no way to control it. I wrote a small tool to install pure Ada libraries: http://www.dmitry-kazakov.de/ada/gps_installer.htm But I would not consider this or similar as a solution, even approximately. > This is not unique to Ada. Perl also has packages that require non-Perl > libraries to be available, like XML::LibXML and Text::CSV::XS. The first > has a dependency on libxml2, the second brings its own C code that must > be compiled and then accessed from the Perl module. > > In both cases a hard build dependency on a working gcc environment > exists; it is the end-user's responsibility to make sure it does exist > and that the proper header files for the dependencies are installed. If that can be user responsibility then everything else can be as well. > Really, this is not a new issue. It is solvable, if you let go of the > NIH mentality. I would be glad to see a workable solution. The one where everything beyond trivial is user responsibility is already there. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de