I'd rather not cause a build machine flag-day to require everyone to
upgrade to 171 by taking the old entries out though - they shouldn't
cause any harm.
Yes, that's a good point. I'll adjust my proposed change as part of the
build 171 resync to include the entries I've recently removed due to
renames and to the upcoming changes for 172 due to the "renames" that
are taking place in 171. Here's the diff:
diff -r b47e1f7cc268 src/pkg/external_deps.pkglintrc
--- a/src/pkg/external_deps.pkglintrc Thu Jul 28 16:38:22 2011 -0700
+++ b/src/pkg/external_deps.pkglintrc Thu Jul 28 20:40:06 2011 -0700
@@ -17,18 +17,26 @@
pkg:/developer/build/onbld
pkg:/developer/gnome/gettext
pkg:/developer/gnome/gnome-doc-utils
+ pkg:/developer/object-file
pkg:/developer/python/pylint
pkg:/developer/versioning/mercurial
pkg:/gnome/config/gconf
pkg:/gnome/theme/hicolor-icon-theme
pkg:/library/python-2/cherrypy
+ pkg:/library/python-2/cherrypy-26
pkg:/library/python-2/coverage
+ pkg:/library/python-2/coverage-26
pkg:/library/python-2/locale-services
pkg:/library/python-2/m2crypto
+ pkg:/library/python-2/m2crypto-26
pkg:/library/python-2/mako
+ pkg:/library/python-2/mako-26
pkg:/library/python-2/ply
+ pkg:/library/python-2/ply-26
pkg:/library/python-2/pybonjour
+ pkg:/library/python-2/pybonjour-26
pkg:/library/python-2/pycurl
+ pkg:/library/python-2/pycurl-26
pkg:/library/python-2/pygobject-26
pkg:/library/python-2/pygtk2-26
pkg:/library/python-2/pyopenssl-26
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
