public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH 1/6] glep-0078: Replace "basename" with non-ambiguous explanation
Date: Wed, 21 Sep 2022 20:16:46 +0200	[thread overview]
Message-ID: <20220921181651.39370-2-mgorny@gentoo.org> (raw)
In-Reply-To: <20220921181651.39370-1-mgorny@gentoo.org>

It has been pointed out that the "basename" term may be ambiguous
in the context.  Explain explicitly that it is the filename with
.gpkg.tar suffix stripped.

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0078.rst | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/glep-0078.rst b/glep-0078.rst
index 05ceba9..24c5c9d 100644
--- a/glep-0078.rst
+++ b/glep-0078.rst
@@ -7,8 +7,9 @@ Type: Standards Track
 Status: Accepted
 Version: 1
 Created: 2018-11-15
-Last-Modified: 2022-08-14
-Post-History: 2018-11-17, 2019-07-08, 2021-09-13, 2021-09-22, 2022-05-28
+Last-Modified: 2022-09-21
+Post-History: 2018-11-17, 2019-07-08, 2021-09-13, 2021-09-22, 2022-05-28,
+              2022-09-21
 Content-Type: text/x-rst
 ---
 
@@ -193,10 +194,11 @@ The gpkg package container is an uncompressed .tar achive whose filename
 should use ``.gpkg.tar`` suffix.
 
 The archive contains a number of files.  All package-related files
-should be stored in a single directory whose name matches the basename
-of the package file.  However, the implementation must be able to
-process an archive where the directory name is mismatched.  There should
-be no explicit archive member entry for the directory.
+should be stored in a single directory whose name matches the package
+filaname after stripping the ``.gpkg.tar`` suffix.  However,
+the implementation must be able to process an archive where
+the directory name is mismatched.  There should be no explicit archive
+member entry for the directory.
 
 The package directory contains the following members, in order:
 
-- 
2.37.3



  reply	other threads:[~2022-09-21 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 18:16 [gentoo-dev] [PATCH 0/6] glep-0078: Clarifications Michał Górny
2022-09-21 18:16 ` Michał Górny [this message]
2022-09-22  6:07   ` [gentoo-dev] [PATCH 1/6] glep-0078: Replace "basename" with non-ambiguous explanation Ulrich Mueller
2022-09-21 18:16 ` [gentoo-dev] [PATCH 2/6] glep-0078: Link tar format to the respective standards Michał Górny
2022-09-21 18:16 ` [gentoo-dev] [PATCH 3/6] glep-0078: Link compressed file formats to GLEP 74 Michał Górny
2022-09-21 18:16 ` [gentoo-dev] [PATCH 4/6] glep-0078: Link OpenPGP to RFC 4880 Michał Górny
2022-09-21 18:16 ` [gentoo-dev] [PATCH 5/6] glep-0078: Clarify that Manifest is signed too Michał Górny
2022-09-21 18:16 ` [gentoo-dev] [PATCH 6/6] glep-0078: Clarify that Manifest must be present for signed binpkg Michał Górny

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=20220921181651.39370-2-mgorny@gentoo.org \
    --to=mgorny@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