Mailinglist Archive: zypp-devel (83 mails)
| < Previous | Next > |
Re: [zypp-devel] Re: [zypp-commit] r10412 - in /trunk/libzypp/zypp: Patch.cc Patch.h sat/SolvAttr.cc sat/SolvAttr.h
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Fri, 20 Jun 2008 15:40:59 +0200
- Message-id: <20080620134059.GB13555@xxxxxxxxxxxxx>
* Michael Andres <ma@xxxxxxx> [Jun 19. 2008 18:37]:
Ah, so this attribute is indeed per-patch and retrieves its value from
updateinfo.xml. Then the current implementation is fine.
We have to find out if and how per-patch messages can be used when we
target 'rpm-only' maintenance in Code11. But thats a different thread ;-)
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
On Thu, Jun 19, Klaus Kaempf wrote:
This only supports a single message per patch.
Beginning with openSUSE 11.0, messages belong to packages and a
package can have multiple messages.
Since patches are collection of packages, the 'message' attribute of a
patch should be an iterator.
This is just the backport of what was implemented in zypp/satsolver
for 11.0 in order to be able to compile trunk.
AFAIK the message from updateinfo.xml is implemented as a patch
attribute ("update:message") and provided as string attribute in
the solv file. Similar to the patch description.
Ah, so this attribute is indeed per-patch and retrieves its value from
updateinfo.xml. Then the current implementation is fine.
Maybe the implementation is insufficient.
We have to find out if and how per-patch messages can be used when we
target 'rpm-only' maintenance in Code11. But thats a different thread ;-)
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |