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.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no 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!.POSTED!not-for-mail
From: Georg Bauhaus <bauhaus@futureapps.invalid>
Newsgroups: comp.lang.ada
Subject: Re: Ada package registry?
Date: Wed, 3 Feb 2016 10:39:04 +0100
Organization: A noiseless patient Spider
Message-ID: <n8shmd$vbn$1@dont-email.me>
References: <02241ec4-0f95-4f63-9abc-092f167eb59e@googlegroups.com>
 <0ed849e7-75aa-4b9c-8085-ba50014ac87c@googlegroups.com>
 <n8ou60$6p0$1@loke.gir.dk>
 <5e723414-8c8d-4487-87ac-60d95e1b4e01@googlegroups.com>
 <a3dd6b71-c416-403f-a88c-2f573aa4b96f@googlegroups.com>
 <a1c1714b-ddfa-4b40-b53b-f775405222cc@googlegroups.com>
 <93675034-4240-4796-a5d5-ed094af3e350@googlegroups.com>
 <73a9036e-535f-4288-987f-d983fc0afe18@googlegroups.com>
Reply-To: nonlegitur@futureapps.de
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 3 Feb 2016 09:36:13 -0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="20cc9b851b49486136ef6d4baef4823a";
	logging-data="32119"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/hADwatqgvEyvrlhKF1YOj3dcGnKhkK3E="
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.5.1
In-Reply-To: <73a9036e-535f-4288-987f-d983fc0afe18@googlegroups.com>
Cancel-Lock: sha1:Cbj76ILcMS0NqyJC56bt6cqVJaA=
Xref: news.eternal-september.org comp.lang.ada:29333
Date: 2016-02-03T10:39:04+01:00
List-Id: <comp.lang.ada>

On 03.02.16 05:21, Shark8 wrote:
> On Tuesday, February 2, 2016 at 2:32:16 PM UTC-7, gautier...@hotmail.com wrote:
>>
>> So perhaps you are thinking about a specialized archive manager (for instance a special version of AZip, to stay with Ada stuff :-) ), which would grab packages or libraries from an Ada-centric repository, running on the programmer's computer?
>
> Closer but not quite.
> The way I envision it would be essentially three programs:
> (1) the 'server', which contains the library, stored in an IR;
> (2) the 'client', which pulls the info from the library and inserts it into the Ada environment,
> (3) the 'project-manager', which takes the library/module on the hosting computer, compiles it, and submits it to the 'server'.
>

(2a) the 'client', which also produces a library archive ready for pushing,
one that follows a simple "standard".

The setup is easier when there is a small, agreed-upon set of requirements,
I think, such as

- P, by default, can be built with

     pragma Restrictions (No_Implementation_*)

- [optional] P is a leaf, it can be built with

      pragma Restrictions (No_Dependence)

- there are test/example programs for P which can be built after P has been
    added to the normal Ada library

Note that the first item has "by default", which is an opportunity for
vendors to put incentives into non-default editions (think: edition for Win32,
edition for proprietary OS, ...).

If this scheme is simple, then, still, complexity may be seen as an opportunity
by sales personnel, since the technical staff is payed for handling that complexity
on behalf of the vendor's customers. No other vendor can handle the same instance
of complexity. Which will be different when it is an instance of simplicity.
Yet, the is a "by default" edition, mentioned earlier, for a freemium library,
maybe.

At all costs, avoid the complexity of Linux style package management whenever
there is a chance of it becoming Ubuntu style package management. ("How to force
a dense graph of half-maintained packages, even when 'Recommended' dependences
are turned off.") Unless, of course, you can sell Ubuntu, too.