eric
eric i don't know how you declare your DESTDIR variable, but the the makefile respect this variable.
# 1st I export it as an env
export DESTDIR="${ED}"
# $ED is a variable provided by the build system. It points somewhere into "/var/tmp/portage/${pkg}/"; Other packages like 66 itself respect that just as expected.
# emake is a build-system-provided function which passes DESTDIR as a make variable; I have paseed to it once again
emake DESTDIR="${ED}"
So the variable is all over the place. I even added before calling make a call to sed to replace dst=$2 with dst=${DESTDIR}/$2 in tools/install.sh. Still fruitless. The output shows "Access denied: /usr/share/66/..." as if DESTDIR isn't respected at all.
eric This is obviously used to build the package on Obarun.
I have checked that.
But IDK why it doesn't work here.
I have added echo "DESTDIR=${DESTDIR} ED=${ED}" to the buildscript before calling make, and the variables are correctly configured. (but make fails)
Wait, I'll try to just configure the build stage with just /usr/bin/true (basically not do anything) and do everything in the install (to DESTDIR) stage itself.
eric Please, if you find a problem with it, open an issue on the git project about it.
I will open an issue if I find a traceable problem.
eric Is not, it's declared to /run/66/log. It's not possible to declare it to /var/log/66 as we are at boot time and the /var/log may not already have write access.
Sorry, my mistake here.
eric 66-yeller only report some information given at its own command line. 66-yeller is not responsible of the destination of the output of the service. If the command executed in your Execute field output something and you declare StdOut=/dev/null, you will not see the output of the command.
What is 66-yeller's -1 argument then? Many fronetnds have a 66-yeller -cdp some-oneshot-in-boot-at -1 /dev/console whatever message as output line, and there's literally no other output (no other command to begin with). Example canopy.
What lines of text do the s6-log processes here manage?
Sorry if I'm wrong, I'm assuming that the -1 /dev/console option output to the active TTY.
eric I don't get your point here.
There are s6-log processes running, hooked up into processes which use 66-yeller with -1 /dev/console.
I don't think many services will have any logs to be processed. (See literally the *-branch and canopy)
eric I don't know what your mean here. Personally i prefer to call a script instead of writing the script inside the Execute field. If you need to change something, you must rewrite the service. If you call a script, you can do whatever the changes you need without the necessity to rewrite the service. It's a matter of choices here.
This script just loads kernel modules mentioned in files in 3 directories, and maybe ignore some files from a directory of lower precedence as the same file exists in higher precedence. What possibly would many users want to edit?
"Rewrite the script" for many is not much easier than "Rewrite the service". Both are packaged. Both need to be copied to a different directory to avoid being overwritten by the package manager.
I personally think that it is easier for users to copy the frontend and edit it, than to find a place for the script, edit it, and edit the frontend's anyways to the new modules.sh.
eric You can make an MR with your changes, it will be appreciated :).
Soon. Not too soon, but soon. Once the gentoo's 66 ecosystem is ready to the extent that I can myself use it.
eric That the advantage of the boot service, you can configure it as you want/need :).
Sorry, I wrote it wrong.
The issue is that many users would like to configure their TZ as a symlink /etc/localtime pointing to /usr/share/zoneinfo/${TZ} rather than a global variable TZ (Not me, but I'd like to support all possible).
A similar story with KEYMAP and FONT; But users have no issue there as anyways those are highly init-specific. (Though, I will soon MR for using init-agnostic files like /etc/vconsole.conf; Again, after I start using gentoo exclusively with 66.)
