On 12/15/22 20:08, Duncan wrote:
Florian Schmaus posted on Thu, 15 Dec 2022 21:40:19 +0100 as excerpted:On 15/12/2022 21.10, Toralf Förster wrote:On 12/15/22 20:22, Florian Schmaus wrote:o use PORTDIR_OVERLAY and multiple repositories on their system: a system-wide, managed by portage, and a dev repository (in your HOME), scoped in via PORTDIR_OVERLAY.Isn't this covered by /etc/portage/repos.conf/*Absolutely, but this requires a manual intervention from the user. And, of course, you can totally opt-out from portage managing (syncing) the repository, but then you have to take care of syncing yourself. The point is that with the new portage release, portage's behavior changes. And I would argue that portage should not, in its effort to become more user friendly, disregard ebuild-developer friendliness. Assuming it is achievable with a reasonable amount of additional code complexity.This bit me too, and making things worse, the truncate killed the git history that presumably had the answer I needed to fix it up. =:^( Fortunately I had a bit of a clue due to preemptively following the portage changelog where I had seen a hint, so I was able to dig it up again without the git log help that's definitely now my first instinct.
Thankfully, if anyone does accidentally gets shallowed, just executing 'git fetch --unshallow' will revert the default '--depth 1'
I really don't care for that 'git clean' patch. If that makes it in without a way to opt-out, it will be patched out for me personally.
Brian
OpenPGP_signature
Description: OpenPGP digital signature
