Danek Duvall wrote:

> I was toying with pkgsend and a couple of non-relocatable SVr4 packages
> recently, and thought about fixing a couple of bugs.  One thing that
> occurred to me was that the current output of pkgsend generate against an
> SVr4 package isn't especially useful.  Specifically, the path to the source
> file on disk (the action "hash") is emitted relative to the "reloc"
> directory.  This is okay if you only have relocatable packages, and you can
> publish your manifest pointing at the reloc directory as the proto area,
> but if you have files coming from both the relocatable area ("reloc") and
> the non-relocatable area ("root"), then it's useless.
> 
> It's pretty straightforward to emit the path of the files relative to the
> parent directory of the package itself, so you get
> 
>     file SUNWfoo/reloc/bin/something path=opt/foo/bin/something mode=...
>     file SUNWfoo/root/etc/foo.conf path=etc/foo.conf mode=...
> 
> Clearly this is meaningless with faspac'ed or datastream packages, but for
> everything else, it makes some amount of sense.
> 
> Thoughts?

This might be

    17769 SVR4 conversion assumes BASEDIR is prepended to source

Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to