[haiku-bugs] Re: [Haiku] #14927: HaikuDepot doesn't show any packages

  • From: "Haiku" <trac@xxxxxxxxxxxx>
  • To: undisclosed-recipients: ;
  • Date: Fri, 01 May 2020 11:19:40 -0000

#14927: HaikuDepot doesn't show any packages
--------------------------------------+----------------------------
  Reporter:  KapiX                    |      Owner:  apl-haiku
      Type:  bug                      |     Status:  reopened
  Priority:  normal                   |  Milestone:  Unscheduled
 Component:  Applications/HaikuDepot  |    Version:  R1/Development
Resolution:                           |   Keywords:
Blocked By:                           |   Blocking:
  Platform:  All                      |
--------------------------------------+----------------------------
Comment (by pulkomandy):

 So, I've been digging in RFCs a bit. I would suggest using a tag URI as
 specified in https://tools.ietf.org/html/rfc4151. It would look something
 like this (the scheme requires us to use a past date at which we owned the
 haiku-os.org domain or can proove that it was not registered to anyone
 else, we can pick any, I just went with the current year):

 * tag:haiku-os.org,2020:repositories/haiku/r1beta2 for Haiku
 * tag:haiku-os.org,2020:repositories/haikuports/r1beta2 for Haikuports

 This makes it clear that the "url" is not an http url, while being more
 readable than an UUID.
 Anyone can easily assign their own tags using their own domain name or
 email address when they create a repo.

 The current identifier specifies both the branch name ("master") and a tag
 ("current", I don't know if we stil have per-hrev repos available), should
 this be kept? Tag URIs support fragments, so we could simply do something
 like this:  tag:haiku-os.org,2020:repositories/haiku/r1beta2#hrev12345
-- 
Ticket URL: <https://dev.haiku-os.org/ticket/14927#comment:28>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.

Other related posts: