[haiku-bugs] Re: [Haiku] #16153: [HaikuDepot] Featured packages tab is empty and disabled
- From: "Haiku" <trac@xxxxxxxxxxxx>
- To: undisclosed-recipients: ;
- Date: Wed, 03 Jun 2020 00:29:31 -0000
#16153: [HaikuDepot] Featured packages tab is empty and disabled
--------------------------------------+----------------------------
Reporter: diver | Owner: apl-haiku
Type: bug | Status: new
Priority: blocker | Milestone: R1/beta2
Component: Applications/HaikuDepot | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Platform: All |
--------------------------------------+----------------------------
Comment (by apl-haiku):
Wait, so the icons, tran...
Take the time to view and understand the ERD diagram which will hopefully
show you how the data structure works. You can view that [
https://depot
.haiku-os.org/__docs/images/img-datamodel.pdf here].
The following *manually* curated data is stored per package by name (or
derivative of the name to handle related package name suffixes);
* Iconography
* Screenshots
* Changelog
* Categorization
* Localizations
The following are stored (per package + per repository);
* Prominance (controls the "featured")
Everything arriving in the HPKR is stored (Per package-version + per
repository) including copyrights, licenses, summary, description etc...
I don't think sharing the prominence between the repositories for a given
package makes any sense at all. If you start a "My Own Repository" with
10 packages and HaikuPorts has 1000 packages you will want to handle
prominence for your own repository completely differently. Even master
repository for HaikuPorts will get many new packages over the lifespan of
R1B2 and the prominences will likely end up being quite different after
some months have passed and different packages are arriving in the master.
If HDS is incapable of handling that, the...
...and re-evaluate HDS and HaikuDepot design and architecture
I think calling the entire "design and architecture" of this system into
question is blowing this out of proportion. I would suggest we close this
ticket since it appears to be working properly now that the {{{url}}}
(identifier) values match. Then we should move this discussion to the HDS
mailing list and work through any remaining issues to get this setup. For
example, I could potentially write a SQL script to seed the prominence
values from "master" --> "r1b2" in this unusual "repository forking"
situation.
--
Ticket URL: <
https://dev.haiku-os.org/ticket/16153#comment:42>
Haiku <
https://dev.haiku-os.org>
The Haiku operating system.
Other related posts:
