I'm just *porting* a commend from bug #523448 (slightly edited for this purpose). I've just released 4.0.x the other day and that major update make a departure from bash to zsh. This departure just make it easy to have everthing,--even the extra profile scripts (.zsh files in this case),--fixing a issue mentionned in the previous bug: unability to define function with a variable (bash treat as literal what follow *function* keyword). What the hell is this feature? Well extra profile scripts can be used with simple call by file name (file name hold function name of the same file). So easy! No need to repeat redundent function definitions, as the bash counter part (e.g. the included disk profile has that awful redundant code), to just be able to run some commands from a file. Each extra script file just get sourced in fuction block so it easy to run extra scripts without too much hassle and repetitive/tedious code. There is already a stable 4.0.1 release! Cheers. Reproducible: Always
Version bumped 3.x branch (bash) variant to support the same API as 4.x (zsh) wich now define function for `*.bash' files if found. 4.x get a minor fix with this. Thanks to at least version bump 3.x branch.
Reiterating the request to [34].2.0 because a nice man page was added (with a little clean up.)
BUMP. There is an annoying issue when starting a profile... hprofile could fails stopping a no started profile before doing so--,pitiful failure,--which was fixed on the latest 3.0.x... but still not available on the tree. Please, bump! to not have a broken script while there are functional version available.
BUMP, please reconsider bumping this packages for the previous reasons and... I've just released two major versions in single day yesterday! First one, v5.0.0 left {ba,z}sh behind to adopt POSIX shell conformance and leave the burden of two branches maintenance behind! And this brought a slight API change compared to v[45].0 for good reasons... v[45].0 adopted functions approach instead of using numerous tiny shell scripts ending up by launching *not less* than at *least* half a dozen of shell in order to execute a few lines shell script. --This is the inheritance of the terrible design of v2.0. Enter v6.0! Second, the other terrible inheritance is... the numerous tiny files. We are talking about a (init script) service like API which is used dynamically. So, why the waste of disk space/seek?! There were a (tiny) file to test the appropriate profile to launch (ptest), a file to set/clean up profule {start,stop}--{start,stop}_{pre,post} files in v5.0 or {pre,post}-{start,stop} in v[34].0, the change of name is required with POSIX shell that might issue an issue with function name containing `-' hyphen,--common tiny files as helpers, and <profile>.{start,stop} files in <v6.0 or {start,stop}_<profile> functions in v6.0 API. So yes, the numerous tiny files that were sourced in v[456].0 to define functions were merged into a single functions file--like an init script service file--named <PROFILE>-functions for the same good reasons launching a dozen of shell was thrown away. Effective disk usage (taking 4k as block size of filesystem) was very terrible like the numerous unnecessary disk seeks and unnecessary complexity. Third, `/var/run' is used for runtime files, so a read-only root-filesystem is supported. Each release did not took an hour to get the design right... What took more time was actually test/chencking every thing... So grab 'em while it's hot... and keeping v5.0 might be necessary to keep a similar API to v[34].0! Cheers!
commit 691ba468f287fd05cdc1da65c7465a646e5963e0 Author: Nelo-T. Wallus <nelo@wallus.de> Date: Sat Aug 5 15:31:34 2017 +0200 sys-apps/hprofile: Bump version Package-Manager: Portage-2.3.6, Repoman-2.3.1 Closes: https://github.com/gentoo/gentoo/pull/5304 and earlier
