[haiku-development] Re: [haiku-commits] Re: haiku: hrev50723 - src/tools/get_package_dependencies src/kits/package src/tools/create_repository_config build/jam src
- From: Andrew Lindesay <apl@xxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sat, 03 Dec 2016 09:31:50 +1300
On Sat, 3 Dec 2016, at 03:39, kallisti5 wrote:
You actually never "see" the uuid anywhere except debug output and
it provides an industry standard random and unique identifier.
Hello Alex;
A UUID under a new field "identifier" would be good as an artificial
identifier. If it were desirable to have a more meaningful identifier,
the HDS system has an existing codification arrangement. You can
explore those here [1] in the web interface. Examples would be;
* haikuports_x86
* haikuports_x86_gcc2
* haikuports_x86_64
* clasqm_x86_gcc2
The conceptual repository "haikuports" (encompassing multiple
architectures) just have the architecture removed;
* haikuports
* clasqm
If this naming arrangement were re-used in the operating system side,
the field "code" would be good to use in order maintain consistency of
naming between the two systems.
Let me know your thoughts on this.
cheers.
[1]
https://depot.haiku-os.org/#/repository/haikuports
Other related posts:
- » [haiku-development] Re: [haiku-commits] Re: haiku: hrev50723 - src/tools/get_package_dependencies src/kits/package src/tools/create_repository_config build/jam src - Andrew Lindesay
