Howdy--
If you prefer I update an existing bug report or file a new one, let me
know, but I couldn't decide whether this was an instance of
18235 dependency resolution through symlinks seems broken
or not.
Ali is refactoring linker packages, and moving some libraries from
system/library into a new system/linkers package.
A build on 163 is resulting in several packages with duplicate
dependencies on system/library. A look at the resolved manifests with
pkgdepend resolve -v shows that they're getting system/library@166 from
the set of packages being resolved for (among others) lib/libelf.so.1,
but also getting system/library@163 from the build system for
usr/lib/libelf.so.1.
You can see what's happened by looking in Ali's workspace, where I added
-v to the pkgdepend resolve invocation and did a dmake
packages.i386/checkmf:
/net/coupe/builds/ab196087/newpkg/nightly/usr/src/pkg/packages.i386
(Sorry for the internal-only path; if anybody external wants to look at
what's here, I can tar it up and post it.)
You can ignore the duplicate system/linkers dependency in SUNWcs, that's
a result of both manual and automatic specification of the same dependency.
Any help for Ali to move forward would be appreciated, especially if it
doesn't involve bypassing dependency generation for the libraries that
he's refactoring.
--Mark
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
