public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] cpufrequtils: Remove SERVICES entry for this package - fixes Bug#12933
Date: Wed, 21 Sep 2022 10:27:28 +0200	[thread overview]
Message-ID: <d088a2df-63dd-5c7d-2609-5185422163f7@ipfire.org> (raw)
In-Reply-To: <bbefc37aaddb49054b8953989d1e14a8f9f66bf0.camel@sicho.home>

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

Thanks Robin,

On 20/09/2022 22:22, Robin Roevens wrote:
> I think you missed the install initscripts part lower in the LFS file:
> 
> 	$(call INSTALL_INITSCRIPTS,$(SERVICES))
> 
> should then also be changed to
> 
> 	$(call INSTALL_INITSCRIPTS,cpufreq)
> 
> otherwise the initscript won't be installed as SERVICES is now empty.
Very good catch. I will try and remember to check for the use of 
$(SERVICES) in future when I am changing things.

I will submit an updated patch.

Regards,

Adolf.
> 
> Regards
> Robin
> 
> Adolf Belka schreef op ma 19-09-2022 om 16:51 [+0200]:
>> - 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
>>
>>
> 

-- 
Sent from my laptop

      reply	other threads:[~2022-09-21  8:27 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
2022-09-20 20:22 ` Robin Roevens
2022-09-21  8:27   ` Adolf Belka [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=d088a2df-63dd-5c7d-2609-5185422163f7@ipfire.org \
    --to=adolf.belka@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