Brock Pytlik wrote:
Shawn Walker wrote:
Brock Pytlik wrote:
New webrev:
http://cr.opensolaris.org/~bpytlik/ips-9290-v4/
This looks pretty workable.
In order to use this in the importer,
I'll add a routine in dependencies.py to mimic the function of
list_implicit_deps_for_manifest on a file by file basis, since
that's the way we get them when snagging files from the svr4 pkgs.
That's no problem; it's simple enough.
For handling elf files, I do the following:
# For kernel modules, default path resolution is /platform/<platform>,
# /kernel, /usr/kernel. But how do we know what <platform> would be for
# a given module? Does it do fallbacks to, say, sun4u?
if path.startswith("kernel") or path.startswith("usr/kernel") or \
(path.startswith("platform") and path.split("/")[2] == "kernel"):
if rp:
print "RUNPATH set for kernel module (%s): %s" % \
(path, rp)
if path.startswith("platform"): # add this platform to search
path
rp.append("/platform/%s/kernel" % path.split("/")[1])
# Default kernel search path
rp.extend(("/kernel", "/usr/kernel"))
This helps find dependencies in the platform modules; since the
module is in a platform dir, we know which platform dir in which
to search for dependencies.
I'm perfectly will make any changes needed for the new importer, so
code as it stands should work fine.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
