On 02/ 8/10 11:22 AM, Danek Duvall wrote:
Shawn Walker wrote:

http://cr.opensolaris.org/~swalker/pkg-14250/

The logic looks fine to me.

Is it worth having a test where a package has different pkg.summary and
description attributes and confirm that the summary comes from the former?

Also confirm that a description attribute doesn't make its way into the
package description?

It's also unclear to me why pkg.description is treated specially in api.py
-- can't you just ignore it like most other set actions?

The importer also still produces pkg.description, pkg.summary, and description. Should it stop generating description as part of this fix?

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

Reply via email to