Il 16/09/24 10:42, Mickaël Bucas ha scritto:
Le sam. 14 sept. 2024 à 21:40, ralfconn <mentaden...@yahoo.com> a écrit :
(snip)
All works fine, I cross-build on Host binary packages and then 'emerge
--usepkg' on the Target.
Well, almost all... On the Target I have apache, on the Host not because
I don't need it. Sometimes the update wants to install apache also on
the Host.
For example, today I have:
# emerge-aarch64-unknown-linux-gnu -uDvNa @world
(snip)
Note the lines without 'to /usr/aarch64-unknown-linux-gnu/", these
packages will be installed on Host.
Any ideas why?
thanks
raf
Hi Ralf
One possible explanation is that "www-servers/apache" could be a build
dependency of some other package. However I don't see in the list of
updates any package with this kind of dependency on
"www-servers/apache".
The only one that seems to depend on it is "app-eselect/eselect-php",
but it'd be installed on the host.
[ebuild N ] app-eselect/eselect-php-0.9.9::gentoo USE="apache2
fpm" 54 KiB
Do you install "dev-lang/php" on the target or the host or both ?
php is not on the Host:
# eix -I php apache
No matches found
It is on the Target, as a dependency of www-apps/pihole-admin-lte
(tatsh-overlay) while apache is a dependency of php with USE=apache2.
All as expected.
Looking at the pihole-admin-lte ebuild I find this:
BDEPEND="app-misc/jq app-portage/portage-utils"
RDEPEND="app-admin/sudo
dev-lang/php[fileinfo,filter,gd,intl,session,sqlite,tokenizer]
net-dns/pihole
virtual/httpd-php"
Humm, interesting, jq is another package that crossdev wants to install
on the Host. BDEPEND are build-time dependencies and it is correctly
cross-built on Host but for some reason crossdev wants to build it also
for the Host.
Could it be an issue with the pihole-admin-lte ebuild rather than
apache's? I'd need to understand ebuilds, easier said than done...
raf
