Hi,
I'm experimenting with baselayout-2 and openrc. I stumbled over
something. In my stable system I get this output:
hive ~ # equery belongs env-update.sh
[ Searching for file(s) env-update.sh in *... ]
sys-apps/portage-2.1.4.4 (/usr/lib/portage/bin/env-update.sh)
sys-apps/baselayout-1.12.11.1 (/sbin/env-update.sh)
hive ~ # equery belongs env-update
[ Searching for file(s) env-update in *... ]
sys-apps/portage-2.1.4.4 (/usr/lib/portage/bin/env-update)
sys-apps/portage-2.1.4.4 (/usr/sbin/env-update ->
../lib/portage/bin/env-update)
In my test environment I get this:
(build) hive / # equery belongs env-update.sh
[ Searching for file(s) env-update.sh in *... ]
sys-apps/portage-2.1.4.4 (/usr/lib/portage/bin/env-update.sh)
(build) hive / # equery belongs env-update
[ Searching for file(s) env-update in *... ]
sys-apps/portage-2.1.4.4 (/usr/sbin/env-update ->
../lib/portage/bin/env-update)
sys-apps/portage-2.1.4.4 (/usr/lib/portage/bin/env-update)
portage provides env-update and env-update.sh, which is also provided my
baselayout-1. But neither openrc nor baselayout-2 does provide
env-update or env-update.sh. My problem is, I plan to build a lean
system without portage (or gcc by the way). If I use baselayout-2, I do
not have a way to use env-update(.sh), because it is not there. An older
version of baselayout-2 provided env-update, which was a symbolic link
to /sbin/rc . Does anyone know, how baselayout-2 does now handle
updating env?
Regards,
Marc
--
gentoo-user@lists.gentoo.org mailing list
