Skip to content

Deps: Nested dependencies aren't symlinked/downloaded #112

@obiwac

Description

@obiwac

If we have a dependency tree (for gv) that looks like this:

kos:/home/obiwac/.cache/bob/deps/kos.ae856b9ae362fccb.local
	proto:/home/obiwac/.cache/bob/deps/proto.8aed25a1d18461de.local
		header:/home/obiwac/.cache/bob/deps/header.facdb7cf42c785c3.local
	header:/home/obiwac/.cache/bob/deps/header.facdb7cf42c785c3.local
	umber:/home/obiwac/.cache/bob/deps/umber.b34dcaeec11a942b.git
proto:/home/obiwac/.cache/bob/deps/proto.8aed25a1d18461de.local
	header:/home/obiwac/.cache/bob/deps/header.facdb7cf42c785c3.local
umber:/home/obiwac/.cache/bob/deps/umber.b34dcaeec11a942b.git

The header (local in this case) dependency never gets symlinked, because only the direct deps of gv are downloaded. We should download everything.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions