Opened 9 years ago
Closed 9 years ago
#11969 closed bug (duplicate)
Package build system versions need improved
| Reported by: | kallisti5 | Owned by: | bonefish |
|---|---|---|---|
| Priority: | blocker | Milestone: | R1/beta1 |
| Component: | Servers/package_daemon | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | #10289 | Blocking: | |
| Platform: | All |
Description
Haiku needs to define how package release repositories work. At the moment the ever-increasing hrev tag defines a functional package ecosystem. (This package was built on hrev32452 and should work on any os release newer than hrev32451) These hrev numbers are modified for releases via alpha1~hrev32452. (more details needed)
The package manager needs to sort the release prefix properly
Change History (1)
comment:1 by , 9 years ago
| Blocked By: | 10289 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
On the versionning scheme for Haiku: more details in #10289.
So basically the release will have a version of R1~alpha5.0 or R1~beta1.0 (no hrev info). Anything built for a specific nightly will be R1~alpha5.0~hrev44444, which is greater than the release version number in our versionning scheme.
The package manager needs no change. All packages for a release need to be built while running that release, or an older nightly (which would have a version lile R1~alpha4_pm~hrev33333) so it is installable on alpha5.