[haiku-depot-web] Re: Introduction article

  • From: Stephan Aßmus <superstippi@xxxxxx>
  • To: haiku-depot-web@xxxxxxxxxxxxx
  • Date: Tue, 02 Sep 2014 10:53:03 +0200

Am 02.09.2014 09:48, schrieb Ingo Weinhold:
On 31.08.2014 12:03, Stephan Aßmus wrote:
I wonder why the architecture has to be
provided at all. Isn’t the web-app connected to a single repository,
so the names should be already unique. Even if there are multiple
repositories later, package names should never clash and if two
repositories have packages of the same name, they should be a single
entry in the web app anyway.

Unless I recall incorrectly, the plan was to use the web app as a
central registry for repositories. And in that case there will
definitely be repositories containing the same packages. Some software
can be compiled with different options (take FreeType and the patent
stuff for instance) and we or others will provide differently configured
packages in separate repositories. How they can be subsumed in a single
entry in the web app I haven't though about. Those packages should have
a different summary and description, though.

In the freetype example, wouldn't you have a package with different name, but the same "provides" as the regular freetype package? On the user side, I think one wants to connect to an additional repository, versus switching to a different one, or do you disagree? Then the "patented" repository could contain only those packages for which we would like an alternative version, versus all packages with only some of them actually different. I don't know what is simpler to implement makes less work to maintain, or would be more "expected". If the patented repository contains all packages with only some being actually different, then we have the problem much worse, since for the packages which are not different, we wouldn't want a different description and summary in the web-app. I think differently named packages would be the way to go.

Best regards,
-Stephan



Other related posts: