Mailinglist Archive: zypp-devel (227 mails)
| < Previous | Next > |
Re: [zypp-devel] selecting patches by issue
- From: Michael Matz <matz@xxxxxxx>
- Date: Mon, 14 Apr 2008 14:33:21 +0200 (CEST)
- Message-id: <Pine.LNX.4.64.0804141431180.20583@xxxxxxxxxxxxx>
Hi,
On Mon, 14 Apr 2008, Martin Vidner wrote:
I disagree. A provides is (at best) something which another entity can
require. A provide should not be misused to ease searching. You can
equally well define an fixed format for other random data, e.g. we could
have attributes 'patch:fixes = "bnc#12345"', if we absolutely must.
Ciao,
Michael.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
On Mon, 14 Apr 2008, Martin Vidner wrote:
- Use the solver, and during parsing inject something like
provides:fix(bugzilla:23444) when filling the repodata. Then
applications could inject a requires in the solver
fix(bugzilla:23444) and just solve. I dont't know the consequences
of this.
It is cleaner than having to search the free form description. Now that
I think of it, having the patch metadata in a form different from
Provides seems wrong, because that only forces you to write new code for
what is served by Provides better.
I disagree. A provides is (at best) something which another entity can
require. A provide should not be misused to ease searching. You can
equally well define an fixed format for other random data, e.g. we could
have attributes 'patch:fixes = "bnc#12345"', if we absolutely must.
Ciao,
Michael.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |