From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] sgml-catalog-r1.eclass: New eclass to handle SGML catalogs
Date: Wed, 04 Sep 2019 18:54:56 +0200 [thread overview]
Message-ID: <bd277f39f411b4fc91f937199663771b5df33ebb.camel@gentoo.org> (raw)
In-Reply-To: <w6gpnkg5br2.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 3351 bytes --]
On Wed, 2019-09-04 at 17:20 +0200, Ulrich Mueller wrote:
> > > > > > On Wed, 04 Sep 2019, Michał Górny wrote:
> > +# Copyright 2019 Gentoo Authors
> > +# Distributed under the terms of the GNU General Public License v2
> > +
> > +# @ECLASS: sgml-catalog-r1.eclass
> > +# @MAINTAINER:
> > +# Michał Górny <mgorny@gentoo.org>
> > +# @AUTHOR:
> > +# Michał Górny <mgorny@gentoo.org>
> > +# @BLURB: Functions for installing SGML catalogs
> > +# @DESCRIPTION:
> > +# sgml-catalog-r1 provides postinst/postrm for regenerating
> > +# /etc/sgml/catalog to include all installed catalogs.
>
> catalog...catalog...catalog...
>
> Certainly the style could be improved? How about: "This eclass
> regenerates /etc/sgml/catalog in pkg_postinst and pkg_postrm."?
>
> > +
> > +case "${EAPI:-0}" in
>
> Quotes aren't necessary here.
>
> > + 7)
> > + ;;
> > + *)
> > + die "Unsupported EAPI=${EAPI} for ${ECLASS}"
> > + ;;
> > +esac
>
> This case statement could be more compact (which would be better
> readable, IMHO).
>
> > +
> > +EXPORT_FUNCTIONS pkg_postinst pkg_postrm
> > +
> > +if [[ ! ${_SGML_CATALOG_R1} ]]; then
> > +
> > +RDEPEND=">=app-text/sgml-common-0.6.3-r7"
> > +
> > +# @FUNCTION: sgml-catalog-r1_update_catalog
> > +# @DESCRIPTION:
> > +# Regenerate /etc/sgml/catalog to include all installed catalogs.
> > +sgml-catalog-r1_update_catalog() {
> > + local shopt_save=$(shopt -p nullglob)
> > + shopt -s nullglob
> > + local cats=( "${EROOT}"/etc/sgml/*.cat )
> > + ${shopt_save}
> > +
> > + if [[ ${#cats[@]} -gt 0 ]]; then
> > + ebegin "Updating ${EROOT}/etc/sgml/catalog"
> > + printf 'CATALOG "%s"\n' "${cats[@]}" > "${T}"/catalog &&
> > + mv "${T}"/catalog "${EROOT}"/etc/sgml/catalog
> > + else
> > + ebegin "Removing ${EROOT}/etc/sgml/catalog"
> > + rm "${EROOT}"/etc/sgml/catalog &&
> > + { rmdir "${EROOT}"/etc/sgml &>/dev/null || :; }
> > + fi
> > + eend "${?}"
>
> Using one eend for each ebegin would improve readability. Also, quotes
> around $? aren't necessary.
>
> > +}
> > +
> > +# @FUNCTION: sgml-catalog-r1_update_env
> > +# @DESCRIPTION:
> > +# Regenerate environment variables and copy them to env.d.
> > +sgml-catalog-r1_update_env() {
> > + # gensgmlenv doesn't support overriding root
> > + if [[ -z ${ROOT} && -x "${EPREFIX}/usr/bin/gensgmlenv" ]]; then
> > + ebegin "Regenerating SGML environment variables"
> > + gensgmlenv &&
> > + grep -v export "${EPREFIX}/etc/sgml/sgml.env" > "${T}"/93sgmltools-lite &&
> > + mv "${T}"/93sgmltools-lite "${EPREFIX}/etc/env.d/93sgmltools-lite"
> > + eend "${?}"
> > + fi
> > +}
> > +
> > +# @FUNCTION: sgml-catalog-r1_pkg_postinst
> > +# @DESCRIPTION:
> > +# Perform catalog post installation tasks.
>
> Sure, what else would postinst do? :)
Exactly. I was wondering if it would be good style to just skip
documenting this.
>
> > +sgml-catalog-r1_pkg_postinst() {
> > + sgml-catalog-r1_update_catalog
> > + sgml-catalog-r1_update_env
> > +}
> > +
> > +# @FUNCTION: sgml-catalog-r1_pkg_postrm
> > +# @DESCRIPTION:
> > +# Perform catalog post removal tasks.
> > +sgml-catalog-r1_pkg_postrm() {
> > + sgml-catalog-r1_update_catalog
> > + sgml-catalog-r1_update_env
> > +}
> > +
> > +_SGML_CATALOG_R1=1
> > +fi
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-09-04 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 12:38 [gentoo-dev] [PATCH] sgml-catalog-r1.eclass: New eclass to handle SGML catalogs Michał Górny
2019-09-04 15:20 ` Ulrich Mueller
2019-09-04 16:54 ` Michał Górny [this message]
2019-09-05 11:37 ` [gentoo-dev] [PATCH v2] " 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=bd277f39f411b4fc91f937199663771b5df33ebb.camel@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