Please, pretty please, ship the three files with the 'linux-cpupower' package, setting the systemd service disabled by default.[...]
Let's fix this bug once and for all!
On Sat, 28 Dec 2024 17:52:44 +0100 Francesco Poli wrote:
[...]
Please, pretty please, ship the three files with the 'linux-cpupower' package, setting the systemd service disabled by default.
Let's fix this bug once and for all![...]
Is there any chance to see the three files included in the
'linux-cpupower' package?
Please my previous [message], for more details.
[message]: <https://bugs.debian.org/894906#94>
Thanks for your time and patience.
On Mon, Mar 10, 2025 at 07:25:37PM +0100, Francesco Poli wrote:[...]
[...]Is there any chance to see the three files included in the
'linux-cpupower' package?
Let me try to quickly summarize the status here (don't shoot the
messenger):
From a src:linux maintenance point of view I think we would still
continue to decline shipping some scripts in packages produced, but
there might be a chance we ship them if they are maintained upstream
as examples (FWIW, this is very similar argument as it holds for which patches we accept to cherry-pick, only what is reviewed and accepted
upstream and is applied in at least a upper version)
My proposal to you would be: Do upstream the scripts as part of the tools/power/cpupower source. If they get accepted we might include them
as part of upstream as well in the produced packages.
On Mon, 17 Mar 2025 21:21:53 +0100 Salvatore Bonaccorso wrote:
[...]
On Mon, Mar 10, 2025 at 07:25:37PM +0100, Francesco Poli wrote:[...]
[...]Is there any chance to see the three files included in the 'linux-cpupower' package?
Let me try to quickly summarize the status here (don't shoot the messenger):
From a src:linux maintenance point of view I think we would still
continue to decline shipping some scripts in packages produced, but
there might be a chance we ship them if they are maintained upstream
as examples (FWIW, this is very similar argument as it holds for which patches we accept to cherry-pick, only what is reviewed and accepted upstream and is applied in at least a upper version)
My proposal to you would be: Do upstream the scripts as part of the tools/power/cpupower source. If they get accepted we might include them
as part of upstream as well in the produced packages.
Hello Salvatore,
thanks for your followup.
I can try, hoping that the answer won't be "this is a job for distros,
not for upstream!"...
Where do I start from?
By sending a message to the [linux-pm] mailing list?
[linux-pm]: <https://lore.kernel.org/linux-pm/>
Please let me know, thanks for your time.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 482 |
Nodes: | 16 (2 / 14) |
Uptime: | 50:35:14 |
Calls: | 9,566 |
Files: | 13,660 |
Messages: | 6,142,410 |