On 06/27/12 20:15, Tim Foster wrote:
On 06/28/12 01:42 PM, Brock Pytlik wrote:
In short, now if I want to ensure that I have a pkglint clean
repository, it's not sufficient to pkglint all my packages against that
repository and each other any time I'm publishing a group of packages.
Instead, I have to wait until all the packages have been published, then
run pkglint over the repository and that repository now must be a
staging repo (that's a duplicate of my full repo) since I may need to
roll back publication of some packages to fix some pkglint issue.
Thoughts?
Yep. I understand your concern.
I think I might be able to make this work - we're already maintaining
a set of all the packages that have been marked as obsolete or
renamed, but you really want the reverse: whenever we publish any
package, if it's obsolete, check that no packages in the repository
(or those being linted) depend on that package.
Right, that's what I was trying to ask for :)
(Just as a note, the packages being linted currently would get caught by
what's already in the changeset, right?)
I'll investigate whether this is feasible...
Thanks,
Brock
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
