This is here to track the fixes we need to make in gentoo for programs that source /etc/init.d/functions.sh. This is going away, so all programs that use it should start testing for the presence of /lib/gentoo/functions.sh. If this file exists, source it instead of /etc/init.d/functions.sh. To set up to test to make sure your program works with this new file, you should run: emerge -1 gentoo-functions When yu make the fix, please do not add a hard dependency to sys-apps/gentoo-functions. The plan is to add this package to @system as soon as it goes stable. No more chatter in this bug please; just add dependencies.
After some discussion on the list, it was determined that if you add hard dependencies to your package for sys-apps/Gentoo-functions, we do not need to add it to @system at all, so go ahead and do that.
hal, please, one bug per package, as the package maintainer will obviously create a new revision (or version) and fix everything involved ending up in file system no need to reply to this message to avoid bugspam on the Tracker
Hello. It seems like all the activity about fixing this problem has stopped: for example, even though a new version of glibc was added to portage in November 2014 it doesn't seem like it uses a valid way to functions.sh. Probably it would be correct to make gentoo-functions package also create a symlink to /etc/init.d/functions.sh?
Removing bugs for maintainer-use scripts. We need not to care about those.
9 months (and 17 months in case of glibc) is much too long. Time to make this a QA business. I'm going to set a deadline on all bugs.
some weeks too late but happy birthday,tracker!
> I'm going to set a deadline on all bugs. When deadline?
Anybody alive?
Seems like this bug depends on no bugs in really important packages. Probably, it is possible to just mark it as resolved?
(In reply to Michał Górny from comment #5) > 9 months (and 17 months in case of glibc) is much too long. Time to make > this a QA business. I'm going to set a deadline on all bugs. What is the current state? You set a deadline, the deadline is ended more than six month before. I recently run into trouble with #504118, so I created the symlink again. Could "we" be informed, why this is so difficult to replace a file with some function definitions? I think there are some problems caused that delay, but I would like which one.
Oh my god, nothing yet? Why?
We simply have a lot of other work to do, and pursuing all of this is at least hard. If you would like to help, please take a look at the remaining bugs. Preferably create pull requests for the relevant ebuilds, and I will merge them ASAP.
It's fixed now.
To move forward on this, somebody needs to verify that all of the dependencies have been stabilized.
Created attachment 468990 [details, diff] startDM.sh-patch Why not simply bail out on non openerc systems ?
Comment on attachment 468990 [details, diff] startDM.sh-patch Sorry, wrong bug number
This bug is now open for more than 3 years and we' running for the 4th aniversary. May I suggest to do a harder escalation on fixing this, for example: * Packages that don't fix this with the next release won't get the tagged stabilized * Packages that don't fix this until 2018-3-10 get pushed out of the portage rep
So! Only openrc remains! Good!
