Opened 6 years ago

Closed 5 years ago

#10287 closed enhancement (fixed)

Include "haiku" repository by default

Reported by: mmadia Owned by: bonefish
Priority: normal Milestone: R1/beta1
Component: Build System Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

http://www.haiku-files.org/haiku/master/repo/ contains the HPKG's built by Haiku's build system via jam -q @release-raw build \<repository\>haiku . It is intended for that to be a mirror of http://packages.haiku-os.org/haiku/master/repo/ (which doesn't yet exist).

HaikuDepot should determine the host system <arch> and <version> and add the appropriate repo to its list. It should also include the <arch>/<current>/ directory as well.

The former URL will allow users to grab missing packages -- e.g., someone built a custom image and left out haiku_devel or webpositive. IIRC, the later will assist with keeping packages updated to the newest version.

The following snippet from build/scripts/build_haiku_repository shows one method of determining <arch> and <version>

# prepare the repo info file
fileName=`basename "$packageDir"/haiku-*.hpkg .hpkg`
version=${fileName#*-}
version=${version%%-*}
arch=${fileName##*-}

Change History (4)

comment:1 Changed 6 years ago by anevilyak

This might actually make more sense to do at build time, as the list of available repositories is a system-wide setting, and not actually specific to depot.

comment:2 Changed 6 years ago by bonefish

Indeed, the plan is to add the repository at build time, just like it is already done for the HaikuPorts repository. In this case it won't be possible to already add the repository cache file (only the repository info). That is buildbot could probably do that, depending on the order in which it builds repository and images.

comment:3 Changed 6 years ago by anevilyak

Component: Applications/HaikuDepotBuild System
Owner: changed from stippi to bonefish

comment:4 Changed 5 years ago by bonefish

Resolution: fixed
Status: newclosed

Implemented in hrev46706.

Note: See TracTickets for help on using tickets.