Bug 36377 - New ebuild: app-admin/hprofile
|
Bug#:
36377
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: base-system@gentoo.org
|
Reported By: optilude@gmx.net
|
|
Component: Ebuilds
|
|
|
URL:
http://hprofile.sourceforge.net
|
|
Summary: New ebuild: app-admin/hprofile
|
|
Keywords: EBUILD
|
|
Status Whiteboard:
|
|
Opened: 2003-12-23 10:32 0000
|
Hello,
Submitting an ebuild for my hprofile system, found at http://hprofile.sourceforge.net. The ebuild installs the scripts to /usr/sbin, installs an example /etc/hprofile configuration directory, and Gentoo init scripts in /etc/init.d. The file /etc/runlevels/boot/.critical is also created or updated, since the 'hprofile' init script needs to be run during the "critical" stages of boot (notably before 'modules').
Please note - my initial tests suggest that the mechanisms in /sbin/rc that check for "critical" runlevels completely disregard dependencies among these scripts. Bug or feature? In any case, I'm not sure how this would react if the 'hprofile' init script was not added to the 'boot' runlevel. With the default installation by the ebuild, this won't do any harm (since the default boot profile does not switch any configuration files or change the state of the system in any way), but it may be a little confusing for users if the hprofile boot script is started even if they do 'rc-update del hprofile'...
I'll try to look into this again later and report again here if I find out more.
Reproducible: Always
Steps to Reproduce:
Just thought I'd clarify, hprofile is a set of bash scripts to manage
"profiles" of things like hardware configuration (dependent on configuration
files), power usage (processor speed, LCD brightness etc.), networks (network
configuration files, interfaces and services), and anything else where you need
to switch configuration files around, start/stop services and run commands to
put the system in a specific "profile".
The tarball the ebuild intalls comes with Gentoo init scripts that can make all
this highly automated, meaning the correct profile can be automatically
determined and configured at bootup, or by running a single command.
hprofile is in some ways similar to quickswitch, but it's more general (and
probably more flexible), and in my opinion a lot easier to use and configure.
I really think this should be added to portage, I am currently setting up a
hprofile system and it looks promising.
Just my two cents...
2.0_beta2 is now in portage
