From 4d02382cb2d57c75400b757aa76e49ef931a3d29 Mon Sep 17 00:00:00 2001 From: Anderson Torres Date: Wed, 25 Oct 2023 23:32:22 -0300 Subject: [PATCH] Add prior art section Also, add extra links --- rfcs/0146-meta-categories.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/rfcs/0146-meta-categories.md b/rfcs/0146-meta-categories.md index 0f59fc0..65e439a 100755 --- a/rfcs/0146-meta-categories.md +++ b/rfcs/0146-meta-categories.md @@ -244,6 +244,16 @@ The most immediate drawbacks are: - as said above, software collections from pkgsrc to slackbuilds - to organization and preservation (as Software Heritage) +# Prior art +[prior-art]: #prior-art + +As said above, categorization is very traditional among software collections. It +is not hard to cite examples in this arena; the most interesting ones I have +found are listed above (linked at [references section](#references)) + +- FreeBSD Ports; +- Debtags; + # Unresolved questions [unresolved]: #unresolved-questions @@ -273,6 +283,10 @@ Still unsolved is what data structure is better suited to represent a category. - [Reserved categories](https://specifications.freedesktop.org/menu-spec/latest/apas03.html) +- [Appstream](https://www.freedesktop.org/wiki/Distributions/AppStream/) + +- [Debtags](https://wiki.debian.org/Debtags) + - [NetBSD pkgsrc guide](https://www.netbsd.org/docs/pkgsrc/) - Especially, [Chapter 12, Section 1](https://www.netbsd.org/docs/pkgsrc/components.html#components.Makefile)