From: "Göktürk Yüksek" <gokturk@binghamton.edu>
To: devmanual@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [PATCH v2 4/4] ebuild-writing/misc-files/metadata: add an example for slots and subslots
Date: Sat, 14 May 2016 20:57:50 -0400 [thread overview]
Message-ID: <1463273870-28502-5-git-send-email-gokturk@binghamton.edu> (raw)
In-Reply-To: <1463273870-28502-1-git-send-email-gokturk@binghamton.edu>
Signed-off-by: Göktürk Yüksek <gokturk@binghamton.edu>
---
ebuild-writing/misc-files/metadata/text.xml | 50 +++++++++++++++++++++++++++++
1 file changed, 50 insertions(+)
diff --git a/ebuild-writing/misc-files/metadata/text.xml b/ebuild-writing/misc-files/metadata/text.xml
index 3d135a6..486af11 100644
--- a/ebuild-writing/misc-files/metadata/text.xml
+++ b/ebuild-writing/misc-files/metadata/text.xml
@@ -549,6 +549,56 @@ is demonstrated.
</body>
</subsubsection>
+<subsubsection>
+<title>Slots and Subslots</title>
+<body>
+
+<p>
+The main focus of this example is to demonstrate how slots and
+subslots are specified, by examining the metadata of
+<path>media-libs/libpng</path>. There may be multiple reasons for
+slotting depending on the nature of the package. For this particular
+package, it can be seen that the slots are used to provide different
+versions of the library with varying binary compatibility and that
+developers are advised to build against the slot 0. Furthermore,
+different versions of this package with the same subslot provide the
+same Application Binary Interface (ABI), according to the description
+specified in the <c><subslots></c> tag.
+</p>
+
+<codesample lang="sgml">
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="project">
+ <email>base-system@gentoo.org</email>
+ <name>Gentoo Base System</name>
+ </maintainer>
+ <use>
+ <flag name="apng">support unofficial APNG (Animated PNG) spec</flag>
+ </use>
+ <upstream>
+ <remote-id type="cpe">cpe:/a:libpng:libpng</remote-id>
+ <remote-id type="sourceforge">apng</remote-id>
+ </upstream>
+ <slots>
+ <slot name="0">
+ For building against. This is the only slot
+ that provides headers and command line tools.
+ </slot>
+ <slot name="1.2">
+ For binary compatibility, provides libpng12.so.0 only.
+ </slot>
+ <slot name="1.5">
+ For binary compatibility, provides libpng15.so.15 only.
+ </slot>
+ <subslots>Reflect ABI compatibility for libpng.so.</subslots>
+ </slots>
+</pkgmetadata>
+</codesample>
+
+</body>
+</subsubsection>
</body>
</subsection>
<subsection>
--
2.7.3
prev parent reply other threads:[~2016-05-15 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 0:57 [gentoo-dev] [PATCH v2 0/4] devmanual: update the docs per GLEP 67 and 68 Göktürk Yüksek
2016-05-15 0:57 ` [gentoo-dev] [PATCH v2 1/4] general-concepts/herds-and-projects: update per GLEP 67 #572144 #549490 Göktürk Yüksek
2016-05-15 0:57 ` [gentoo-dev] [PATCH v2 2/4] ebuild-writing/misc-files/metadata: rewrite the section per GLEP 67 #572144 Göktürk Yüksek
2016-05-15 7:54 ` Michał Górny
2016-05-16 2:23 ` Göktürk Yüksek
2016-05-15 0:57 ` [gentoo-dev] [PATCH v2 3/4] ebuild-writing/misc-files/metadata: update wrt slotting and per GLEP 68 Göktürk Yüksek
2016-05-15 0:57 ` Göktürk Yüksek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1463273870-28502-5-git-send-email-gokturk@binghamton.edu \
--to=gokturk@binghamton.edu \
--cc=devmanual@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox