[haiku-development] Re: package_repo question: Why is "any" an invalid architecture for a repo?
- From: Adrien Destugues <pulkomandy@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 10 Aug 2015 20:38:27 +0200
On Mon, Aug 10, 2015 at 01:38:03PM -0400, gus knight wrote:
Hi,
I'm in the final stages of testing the Kitchen, and I just ran into
this:
http://xref.plausible.coop/source/xref/haiku/src/kits/package/RepositoryInfo.cpp#272
Is there any reason that this is a requirement? The easiest thing for
the Kitchen to do would be to have an "any" repository for
arch-independent packages, rather than amalgamating them into all of
the standard architecture repositories.
It is a requirement that all repos you add match the system
architecture. This makes sense to me, and having a single repository is
better than having to add two (native arch + any) on the user side. The
existence of "any" architecture is not something end-users are concerned
with, so they should be in the same repo as other packages.
Note that on our current repo, all packages are stored in a single
directory (
http://packages.haiku-os.org/haikuports/master/hpkg/), then
the repos are just linking to them. This means the packages themselves
are not duplicated.
--
Adrien.
Other related posts:
