Hi Ben,
On Wed, 2010-09-08 at 12:23 -0700, Ben Chang wrote:
> As I mentioned before, I'm very much an IPS newbie and, naturally,
> am not familiar with all of the IPS nomenclature so it was hard to
> understand the man pages. I tried using pkgdepend(1) and got this:
It's worth reading usr/src/pkg/README.pkg in its entirety if you're
making packaging changes. This document explains how ON is using IPS.
In particular, there's a section that explains how the manifest files
themselves are transformed using pkgmogrify, then operated on by
pkgdepend, and then finally published.
You should be testing with
<assuming your build environment is setup correctly>
$ cd $SRC/pkg
$ make -e PKGS=service-network-nis gendeps
which will run pkgmogrify and pkgdepend on the manifest for you, putting
the results in ./packages.<uname -p>/service-network-nis.res. You
should then be able to run pkglint on that .res file individually.
Running the tools on the unprocessed .mf file will not work.
I would also suggest publishing a whole ON build with these changes,
then running pkglint on that repository, looking for errors or warnings
reported for the package you're changing, using:
pkglint -c /tmp/foo -l file://$PKGARCHIVE/repo.redist
but note that the ON build isn't pkglint clean yet, I'm working on it.
Finally installing these bits using ONU, and verifying that the
dependency does indeed appear and works as you expect it to would be
worthwhile (mostly as a learning experience on using onu and how changes
to manifests affect the system)
Hope this helps,
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
