Changes between Initial Version and Version 1 of Ticket #14927, comment 28


Ignore:
Timestamp:
May 1, 2020, 11:24:13 AM (5 years ago)
Author:
pulkomandy

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #14927, comment 28

    initial v1  
    11So, 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):
    22
    3 * tag:haiku-os.org,2020:repositories/haiku/r1beta2 for Haiku
    4 * tag:haiku-os.org,2020:repositories/haikuports/r1beta2 for Haikuports
     3* tag:haiku-os.org,2020:repositories/haiku/r1beta2/x86_gcc2 for Haiku
     4* tag:haiku-os.org,2020:repositories/haikuports/r1beta2/x86_gcc2 for Haikuports
    55
    66This makes it clear that the "url" is not an http url, while being more readable than an UUID.
    77Anyone can easily assign their own tags using their own domain name or email address when they create a repo.
    88
    9 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
     9The 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/x86_gcc2#hrev12345
     10
     11(edited to add the missing CPU architecture)