public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] shadow-utils: Does not depend on gnome-doc-utils
Date: Wed, 22 Feb 2023 10:07:30 +0000	[thread overview]
Message-ID: <399347A2-B922-4565-9D96-329EDA5BC729@ipfire.org> (raw)
In-Reply-To: <20230221174637.925202-1-stefan.schantl@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]

Hello,

I disagree with this patch, as it drops all man pages from this package.

And of course we want man pages.

Would you please update gnome-doc-utils instead?

Best,
-Michael

> On 21 Feb 2023, at 17:46, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> shadow-utils/shadow-utils.nm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/shadow-utils/shadow-utils.nm b/shadow-utils/shadow-utils.nm
> index 1b3be3674..fe3a33273 100644
> --- a/shadow-utils/shadow-utils.nm
> +++ b/shadow-utils/shadow-utils.nm
> @@ -5,7 +5,7 @@
> 
> name       = shadow-utils
> version    = 4.13
> -release    = 1
> +release    = 2
> thisapp    = shadow-%{version}
> 
> groups     = System/Base
> @@ -29,12 +29,12 @@ build
> docbook-xsl
> flex
> gettext-devel
> - gnome-doc-utils
> libacl-devel
> libattr-devel
> libcap-devel
> libtool
> libxcrypt-devel
> + perl(open)
> pam-devel
> end
> 
> -- 
> 2.30.2
> 


      parent reply	other threads:[~2023-02-22 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 17:46 Stefan Schantl
2023-02-21 17:46 ` [PATCH 2/2] gnome-doc-utils: Drop package Stefan Schantl
2023-02-22 10:07 ` Michael Tremer [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=399347A2-B922-4565-9D96-329EDA5BC729@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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