Derick Eddington <[email protected]> writes: > The cause of the issue is same-named metadata which conflicts trying to > exist in the same directory, right? > That's an issue as well, when using a single repository. You could still declare many packages in `pkg-list.scm' in the top-level directory of the `ported' repository, but then you (obviously) have to distribute the entire collection as a single file ("bundle" in dorodango-speak).
> With separate repos for the separate Ported packages, can the metadata exist > in their > subdirectories, i.e. "ported/xyz/.meta"? > That's possible, but I want the metadata to be in the top-level directory of the repository, so you can treat several repositories as a bundle; this makes it possible to do e.g. this: doro --no-config install --bundle /path/to/ported-repos foo This will install `foo' and all dependencies, considering all repositories below /path/to/ported-repos. If you move metadata even one level deeper, you'll lose this ability. However, this is a current (intentional) restriction in dorodango, and I might be convinced to lift it. > If so, it's still almost as easy to manually install: cd > /searched-dir/ported tar -x -f xyz.tar.gz right? > Yes, with the caveat that you'd have to exclude metadata; e.g.: cd /searched-dir/ported && tar -xf foo-0.1.0.tar.gz --exclude=pkg-list.scm Regards, Rotty -- Andreas Rottmann -- <http://rotty.yi.org/>
