From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] cpufrequtils: Remove SERVICES entry for this package - fixes Bug#12933
Date: Mon, 19 Sep 2022 19:18:32 +0200 [thread overview]
Message-ID: <7123D054-E04C-4811-B42E-C6A46CC002B5@ipfire.org> (raw)
In-Reply-To: <20220919145129.6714-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 19 Sep 2022, at 16:51, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - cpufrequtils is a set of "tools" to manage and set cpu freq settings.
> - There is an initscript but this is only loading the cpu dependent kernel modules that
> are required by cpufrequtils.
> - Therefore cpufrequtils is not a service but a set of tools that are used when required.
> - SERVICES line made blank so that this addon does not show up in the services addon table.
>
> Fixes: Bug#12933
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/cpufrequtils | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/cpufrequtils b/lfs/cpufrequtils
> index 752964198..9076a70d7 100644
> --- a/lfs/cpufrequtils
> +++ b/lfs/cpufrequtils
> @@ -34,11 +34,11 @@ DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = cpufrequtils
> -PAK_VER = 11
> +PAK_VER = 12
>
> DEPS =
>
> -SERVICES = cpufreq
> +SERVICES =
>
> ###############################################################################
> # Top-level Rules
> --
> 2.37.3
>
next prev parent reply other threads:[~2022-09-19 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 14:51 Adolf Belka
2022-09-19 17:18 ` Michael Tremer [this message]
2022-09-20 20:22 ` Robin Roevens
2022-09-21 8:27 ` Adolf Belka
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=7123D054-E04C-4811-B42E-C6A46CC002B5@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