Hi, So far crossdev used output overlay as the first one from $(portageq envvar PORTDIR_OVERLAY). Recent addition of repos.conf made it easy to configure overlays without touching the make.conf::PORTDIR_OVERLAY. The order of the overlays in the PORTDIR_OVERLAY now is random (based on name), while $(portageq get_repos /) returns search order, but even from that determine which repository to use as output repository is not deterministic. For now I use a workaround to prepend specific repository for crossdev use as first: /etc/portage/repos.conf/crossdev-local.conf --- [00-crossdev-local] location = /usr/local/portage/crossdev --- I suggest to have a specific repository name for crossdev output, let's say crossdev-local, and get its path using its name: portageq get_repo_path / crossdev-local If not available, then create it(?). Thanks!
if the overlay has not been explicitly specified, then crossdev will do: - portageq get_repo_path / cross-${CTARGET} - portageq get_repo_path / crossdev - default PORTDIR_OVERLAY search (what it does today) i'm not sure i want to bother with picking a default location for generating an overlay. at least not today. http://git.overlays.gentoo.org/gitweb/?p=proj/crossdev.git;a=commitdiff;h=1ed7a8be200dbe4575cc029212f2ee18d0bd5d74
Thanks! I would have also modified the usage, something like: -oO, --ov-output path Overlay to write crossdev package links - [default: first from --overlays list] + [default: by name cross-${CTARGET}, crossdev or + if not found first from --overlays list]
(In reply to Alon Bar-Lev from comment #2) http://git.overlays.gentoo.org/gitweb/?p=proj/crossdev.git;a=commitdiff;h=e1e24c023f85327972ff6e1cbc8762dcca4a1475
